Mock Version: 4.1 Mock Version: 4.1 Mock Version: 4.1 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-100567-64755/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Wrote: /builddir/build/SRPMS/python-django-5.0.8-1.oc9.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-django.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-100567-64755/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-django.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Y2irMt + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-5.0.8 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/5.0.8.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-5.0.8 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + pathfix.py -pni '/usr/bin/python3 -s' . recursedown('.') recursedown('./.github') recursedown('./.github/workflows') recursedown('./.github/workflows/data') recursedown('./.tx') recursedown('./django') recursedown('./django/apps') recursedown('./django/conf') recursedown('./django/conf/app_template') recursedown('./django/conf/app_template/migrations') recursedown('./django/conf/locale') recursedown('./django/conf/locale/af') recursedown('./django/conf/locale/af/LC_MESSAGES') recursedown('./django/conf/locale/ar') recursedown('./django/conf/locale/ar/LC_MESSAGES') recursedown('./django/conf/locale/ar_DZ') recursedown('./django/conf/locale/ar_DZ/LC_MESSAGES') recursedown('./django/conf/locale/ast') recursedown('./django/conf/locale/ast/LC_MESSAGES') recursedown('./django/conf/locale/az') recursedown('./django/conf/locale/az/LC_MESSAGES') recursedown('./django/conf/locale/be') recursedown('./django/conf/locale/be/LC_MESSAGES') recursedown('./django/conf/locale/bg') recursedown('./django/conf/locale/bg/LC_MESSAGES') recursedown('./django/conf/locale/bn') recursedown('./django/conf/locale/bn/LC_MESSAGES') recursedown('./django/conf/locale/br') recursedown('./django/conf/locale/br/LC_MESSAGES') recursedown('./django/conf/locale/bs') recursedown('./django/conf/locale/bs/LC_MESSAGES') recursedown('./django/conf/locale/ca') recursedown('./django/conf/locale/ca/LC_MESSAGES') recursedown('./django/conf/locale/ckb') recursedown('./django/conf/locale/ckb/LC_MESSAGES') recursedown('./django/conf/locale/cs') recursedown('./django/conf/locale/cs/LC_MESSAGES') recursedown('./django/conf/locale/cy') recursedown('./django/conf/locale/cy/LC_MESSAGES') recursedown('./django/conf/locale/da') recursedown('./django/conf/locale/da/LC_MESSAGES') recursedown('./django/conf/locale/de') recursedown('./django/conf/locale/de/LC_MESSAGES') recursedown('./django/conf/locale/de_CH') recursedown('./django/conf/locale/dsb') recursedown('./django/conf/locale/dsb/LC_MESSAGES') recursedown('./django/conf/locale/el') recursedown('./django/conf/locale/el/LC_MESSAGES') recursedown('./django/conf/locale/en') recursedown('./django/conf/locale/en/LC_MESSAGES') recursedown('./django/conf/locale/en_AU') recursedown('./django/conf/locale/en_AU/LC_MESSAGES') recursedown('./django/conf/locale/en_GB') recursedown('./django/conf/locale/en_GB/LC_MESSAGES') recursedown('./django/conf/locale/en_IE') recursedown('./django/conf/locale/eo') recursedown('./django/conf/locale/eo/LC_MESSAGES') recursedown('./django/conf/locale/es') recursedown('./django/conf/locale/es/LC_MESSAGES') recursedown('./django/conf/locale/es_AR') recursedown('./django/conf/locale/es_AR/LC_MESSAGES') recursedown('./django/conf/locale/es_CO') recursedown('./django/conf/locale/es_CO/LC_MESSAGES') recursedown('./django/conf/locale/es_MX') recursedown('./django/conf/locale/es_MX/LC_MESSAGES') recursedown('./django/conf/locale/es_NI') recursedown('./django/conf/locale/es_PR') recursedown('./django/conf/locale/es_VE') recursedown('./django/conf/locale/es_VE/LC_MESSAGES') recursedown('./django/conf/locale/et') recursedown('./django/conf/locale/et/LC_MESSAGES') recursedown('./django/conf/locale/eu') recursedown('./django/conf/locale/eu/LC_MESSAGES') recursedown('./django/conf/locale/fa') recursedown('./django/conf/locale/fa/LC_MESSAGES') recursedown('./django/conf/locale/fi') recursedown('./django/conf/locale/fi/LC_MESSAGES') recursedown('./django/conf/locale/fr') recursedown('./django/conf/locale/fr/LC_MESSAGES') recursedown('./django/conf/locale/fr_BE') recursedown('./django/conf/locale/fr_CA') recursedown('./django/conf/locale/fr_CH') recursedown('./django/conf/locale/fy') recursedown('./django/conf/locale/fy/LC_MESSAGES') recursedown('./django/conf/locale/ga') recursedown('./django/conf/locale/ga/LC_MESSAGES') recursedown('./django/conf/locale/gd') recursedown('./django/conf/locale/gd/LC_MESSAGES') recursedown('./django/conf/locale/gl') recursedown('./django/conf/locale/gl/LC_MESSAGES') recursedown('./django/conf/locale/he') recursedown('./django/conf/locale/he/LC_MESSAGES') recursedown('./django/conf/locale/hi') recursedown('./django/conf/locale/hi/LC_MESSAGES') recursedown('./django/conf/locale/hr') recursedown('./django/conf/locale/hr/LC_MESSAGES') recursedown('./django/conf/locale/hsb') recursedown('./django/conf/locale/hsb/LC_MESSAGES') recursedown('./django/conf/locale/hu') recursedown('./django/conf/locale/hu/LC_MESSAGES') recursedown('./django/conf/locale/hy') recursedown('./django/conf/locale/hy/LC_MESSAGES') recursedown('./django/conf/locale/ia') recursedown('./django/conf/locale/ia/LC_MESSAGES') recursedown('./django/conf/locale/id') recursedown('./django/conf/locale/id/LC_MESSAGES') recursedown('./django/conf/locale/ig') recursedown('./django/conf/locale/ig/LC_MESSAGES') recursedown('./django/conf/locale/io') recursedown('./django/conf/locale/io/LC_MESSAGES') recursedown('./django/conf/locale/is') recursedown('./django/conf/locale/is/LC_MESSAGES') recursedown('./django/conf/locale/it') recursedown('./django/conf/locale/it/LC_MESSAGES') recursedown('./django/conf/locale/ja') recursedown('./django/conf/locale/ja/LC_MESSAGES') recursedown('./django/conf/locale/ka') recursedown('./django/conf/locale/ka/LC_MESSAGES') recursedown('./django/conf/locale/kab') recursedown('./django/conf/locale/kab/LC_MESSAGES') recursedown('./django/conf/locale/kk') recursedown('./django/conf/locale/kk/LC_MESSAGES') recursedown('./django/conf/locale/km') recursedown('./django/conf/locale/km/LC_MESSAGES') recursedown('./django/conf/locale/kn') recursedown('./django/conf/locale/kn/LC_MESSAGES') recursedown('./django/conf/locale/ko') recursedown('./django/conf/locale/ko/LC_MESSAGES') recursedown('./django/conf/locale/ky') recursedown('./django/conf/locale/ky/LC_MESSAGES') recursedown('./django/conf/locale/lb') recursedown('./django/conf/locale/lb/LC_MESSAGES') recursedown('./django/conf/locale/lt') recursedown('./django/conf/locale/lt/LC_MESSAGES') recursedown('./django/conf/locale/lv') recursedown('./django/conf/locale/lv/LC_MESSAGES') recursedown('./django/conf/locale/mk') recursedown('./django/conf/locale/mk/LC_MESSAGES') recursedown('./django/conf/locale/ml') recursedown('./django/conf/locale/ml/LC_MESSAGES') recursedown('./django/conf/locale/mn') recursedown('./django/conf/locale/mn/LC_MESSAGES') recursedown('./django/conf/locale/mr') recursedown('./django/conf/locale/mr/LC_MESSAGES') recursedown('./django/conf/locale/ms') recursedown('./django/conf/locale/ms/LC_MESSAGES') recursedown('./django/conf/locale/my') recursedown('./django/conf/locale/my/LC_MESSAGES') recursedown('./django/conf/locale/nb') recursedown('./django/conf/locale/nb/LC_MESSAGES') recursedown('./django/conf/locale/ne') recursedown('./django/conf/locale/ne/LC_MESSAGES') recursedown('./django/conf/locale/nl') ./setup.py: no change ./django/__init__.py: no change ./django/__main__.py: no change ./django/shortcuts.py: no change ./django/apps/__init__.py: no change ./django/apps/config.py: no change ./django/apps/registry.py: no change ./django/conf/__init__.py: no change ./django/conf/global_settings.py: no change ./django/conf/locale/__init__.py: no change ./django/conf/locale/ar/__init__.py: no change ./django/conf/locale/ar/formats.py: no change ./django/conf/locale/ar_DZ/__init__.py: no change ./django/conf/locale/ar_DZ/formats.py: no change ./django/conf/locale/az/__init__.py: no change ./django/conf/locale/az/formats.py: no change ./django/conf/locale/bg/__init__.py: no change ./django/conf/locale/bg/formats.py: no change ./django/conf/locale/bn/__init__.py: no change ./django/conf/locale/bn/formats.py: no change ./django/conf/locale/bs/__init__.py: no change ./django/conf/locale/bs/formats.py: no change ./django/conf/locale/ca/__init__.py: no change ./django/conf/locale/ca/formats.py: no change ./django/conf/locale/ckb/__init__.py: no change ./django/conf/locale/ckb/formats.py: no change ./django/conf/locale/cs/__init__.py: no change ./django/conf/locale/cs/formats.py: no change ./django/conf/locale/cy/__init__.py: no change ./django/conf/locale/cy/formats.py: no change ./django/conf/locale/da/__init__.py: no change ./django/conf/locale/da/formats.py: no change ./django/conf/locale/de/__init__.py: no change ./django/conf/locale/de/formats.py: no change ./django/conf/locale/de_CH/__init__.py: no change ./django/conf/locale/de_CH/formats.py: no change ./django/conf/locale/el/__init__.py: no change ./django/conf/locale/el/formats.py: no change ./django/conf/locale/en/__init__.py: no change ./django/conf/locale/en/formats.py: no change ./django/conf/locale/en_AU/__init__.py: no change ./django/conf/locale/en_AU/formats.py: no change ./django/conf/locale/en_GB/__init__.py: no change ./django/conf/locale/en_GB/formats.py: no change ./django/conf/locale/en_IE/__init__.py: no change ./django/conf/locale/en_IE/formats.py: no change ./django/conf/locale/eo/__init__.py: no change ./django/conf/locale/eo/formats.py: no change ./django/conf/locale/es/__init__.py: no change ./django/conf/locale/es/formats.py: no change ./django/conf/locale/es_AR/__init__.py: no change ./django/conf/locale/es_AR/formats.py: no change ./django/conf/locale/es_CO/__init__.py: no change ./django/conf/locale/es_CO/formats.py: no change ./django/conf/locale/es_MX/__init__.py: no change ./django/conf/locale/es_MX/formats.py: no change ./django/conf/locale/es_NI/__init__.py: no change ./django/conf/locale/es_NI/formats.py: no change ./django/conf/locale/es_PR/__init__.py: no change ./django/conf/locale/es_PR/formats.py: no change ./django/conf/locale/et/__init__.py: no change ./django/conf/locale/et/formats.py: no change ./django/conf/locale/eu/__init__.py: no change ./django/conf/locale/eu/formats.py: no change ./django/conf/locale/fa/__init__.py: no change ./django/conf/locale/fa/formats.py: no change ./django/conf/locale/fi/__init__.py: no change ./django/conf/locale/fi/formats.py: no change ./django/conf/locale/fr/__init__.py: no change ./django/conf/locale/fr/formats.py: no change ./django/conf/locale/fr_BE/__init__.py: no change ./django/conf/locale/fr_BE/formats.py: no change ./django/conf/locale/fr_CA/__init__.py: no change ./django/conf/locale/fr_CA/formats.py: no change ./django/conf/locale/fr_CH/__init__.py: no change ./django/conf/locale/fr_CH/formats.py: no change ./django/conf/locale/fy/__init__.py: no change ./django/conf/locale/fy/formats.py: no change ./django/conf/locale/ga/__init__.py: no change ./django/conf/locale/ga/formats.py: no change ./django/conf/locale/gd/__init__.py: no change ./django/conf/locale/gd/formats.py: no change ./django/conf/locale/gl/__init__.py: no change ./django/conf/locale/gl/formats.py: no change ./django/conf/locale/he/__init__.py: no change ./django/conf/locale/he/formats.py: no change ./django/conf/locale/hi/__init__.py: no change ./django/conf/locale/hi/formats.py: no change ./django/conf/locale/hr/__init__.py: no change ./django/conf/locale/hr/formats.py: no change ./django/conf/locale/hu/__init__.py: no change ./django/conf/locale/hu/formats.py: no change ./django/conf/locale/id/__init__.py: no change ./django/conf/locale/id/formats.py: no change ./django/conf/locale/ig/__init__.py: no change ./django/conf/locale/ig/formats.py: no change ./django/conf/locale/is/__init__.py: no change ./django/conf/locale/is/formats.py: no change ./django/conf/locale/it/__init__.py: no change ./django/conf/locale/it/formats.py: no change ./django/conf/locale/ja/__init__.py: no change ./django/conf/locale/ja/formats.py: no change ./django/conf/locale/ka/__init__.py: no change ./django/conf/locale/ka/formats.py: no change ./django/conf/locale/km/__init__.py: no change ./django/conf/locale/km/formats.py: no change ./django/conf/locale/kn/__init__.py: no change ./django/conf/locale/kn/formats.py: no change ./django/conf/locale/ko/__init__.py: no change ./django/conf/locale/ko/formats.py: no change ./django/conf/locale/ky/__init__.py: no change ./django/conf/locale/ky/formats.py: no change ./django/conf/locale/lt/__init__.py: no change ./django/conf/locale/lt/formats.py: no change ./django/conf/locale/lv/__init__.py: no change ./django/conf/locale/lv/formats.py: no change ./django/conf/locale/mk/__init__.py: no change ./django/conf/locale/mk/formats.py: no change ./django/conf/locale/ml/__init__.py: no change ./django/conf/locale/ml/formats.py: no change ./django/conf/locale/mn/__init__.py: no change ./django/conf/locale/mn/formats.py: no change ./django/conf/locale/ms/__init__.py: no change ./django/conf/locale/ms/formats.py: no change ./django/conf/locale/nb/__init__.py: no change ./django/conf/locale/nb/formats.py: no change ./django/conf/locale/nl/__init__.py: no change ./django/conf/locale/nl/formats.py: no change ./django/conf/locale/nn/__init__.py: no change ./django/conf/locale/nn/formats.py: no change ./django/conf/locale/pl/__init__.py: no change ./django/conf/locale/pl/formats.py: no change ./django/conf/locale/pt/__init__.py: no change ./django/conf/locale/pt/formats.py: no change ./django/conf/locale/pt_BR/__init__.py: no change ./django/conf/locale/pt_BR/formats.py: no change ./django/conf/locale/ro/__init__.py: no change ./django/conf/locale/ro/formats.py: no change ./django/conf/locale/ru/__init__.py: no change ./django/conf/locale/ru/formats.py: no change ./django/conf/locale/sk/__init__.py: no change ./django/conf/locale/sk/formats.py: no change ./django/conf/locale/sl/__init__.py: no change ./django/conf/locale/sl/formats.py: no change ./django/conf/locale/sq/__init__.py: no change ./django/conf/locale/sq/formats.py: no change ./django/conf/locale/sr/__init__.py: no change ./django/conf/locale/sr/formats.py: no change ./django/conf/locale/sr_Latn/__init__.py: no change ./django/conf/locale/sr_Latn/formats.py: no change ./django/conf/locale/sv/__init__.py: no change ./django/conf/locale/sv/formats.py: no change ./django/conf/locale/ta/__init__.py: no change ./django/conf/locale/ta/formats.py: no change ./django/conf/locale/te/__init__.py: no change ./django/conf/locale/te/formats.py: no change ./django/conf/locale/tg/__init__.py: no change ./django/conf/locale/tg/formats.py: no change ./django/conf/locale/th/__init__.py: no change ./django/conf/locale/th/formats.py: no change ./django/conf/locale/tk/__init__.py: no change ./django/conf/locale/tk/formats.py: no change ./django/conf/locale/tr/__init__.py: no change ./django/conf/locale/tr/formats.py: no change ./django/conf/locale/ug/__init__.py: no change ./django/conf/locale/ug/formats.py: no change ./django/conf/locale/uk/__init__.py: no change ./django/conf/locale/uk/formats.py: no change ./django/conf/locale/uz/__init__.py: no change ./django/conf/locale/uz/formats.py: no change ./django/conf/locale/vi/__init__.py: no change ./django/conf/locale/vi/formats.py: no change ./django/conf/locale/zh_Hans/__init__.py: no change ./django/conf/locale/zh_Hans/formats.py: no change ./django/conf/locale/zh_Hant/__init__.py: no change ./django/conf/locale/zh_Hant/formats.py: no change recursedown('./django/conf/locale/nl/LC_MESSAGES') recursedown('./django/conf/locale/nn') recursedown('./django/conf/locale/nn/LC_MESSAGES') recursedown('./django/conf/locale/os') recursedown('./django/conf/locale/os/LC_MESSAGES') recursedown('./django/conf/locale/pa') recursedown('./django/conf/locale/pa/LC_MESSAGES') recursedown('./django/conf/locale/pl') recursedown('./django/conf/locale/pl/LC_MESSAGES') recursedown('./django/conf/locale/pt') recursedown('./django/conf/locale/pt/LC_MESSAGES') recursedown('./django/conf/locale/pt_BR') recursedown('./django/conf/locale/pt_BR/LC_MESSAGES') recursedown('./django/conf/locale/ro') recursedown('./django/conf/locale/ro/LC_MESSAGES') recursedown('./django/conf/locale/ru') recursedown('./django/conf/locale/ru/LC_MESSAGES') recursedown('./django/conf/locale/sk') recursedown('./django/conf/locale/sk/LC_MESSAGES') recursedown('./django/conf/locale/sl') recursedown('./django/conf/locale/sl/LC_MESSAGES') recursedown('./django/conf/locale/sq') recursedown('./django/conf/locale/sq/LC_MESSAGES') recursedown('./django/conf/locale/sr') recursedown('./django/conf/locale/sr/LC_MESSAGES') recursedown('./django/conf/locale/sr_Latn') recursedown('./django/conf/locale/sr_Latn/LC_MESSAGES') recursedown('./django/conf/locale/sv') recursedown('./django/conf/locale/sv/LC_MESSAGES') recursedown('./django/conf/locale/sw') recursedown('./django/conf/locale/sw/LC_MESSAGES') recursedown('./django/conf/locale/ta') recursedown('./django/conf/locale/ta/LC_MESSAGES') recursedown('./django/conf/locale/te') recursedown('./django/conf/locale/te/LC_MESSAGES') recursedown('./django/conf/locale/tg') recursedown('./django/conf/locale/tg/LC_MESSAGES') recursedown('./django/conf/locale/th') recursedown('./django/conf/locale/th/LC_MESSAGES') recursedown('./django/conf/locale/tk') recursedown('./django/conf/locale/tk/LC_MESSAGES') recursedown('./django/conf/locale/tr') recursedown('./django/conf/locale/tr/LC_MESSAGES') recursedown('./django/conf/locale/tt') recursedown('./django/conf/locale/tt/LC_MESSAGES') recursedown('./django/conf/locale/udm') recursedown('./django/conf/locale/udm/LC_MESSAGES') recursedown('./django/conf/locale/ug') recursedown('./django/conf/locale/ug/LC_MESSAGES') recursedown('./django/conf/locale/uk') recursedown('./django/conf/locale/uk/LC_MESSAGES') recursedown('./django/conf/locale/ur') recursedown('./django/conf/locale/ur/LC_MESSAGES') recursedown('./django/conf/locale/uz') recursedown('./django/conf/locale/uz/LC_MESSAGES') recursedown('./django/conf/locale/vi') recursedown('./django/conf/locale/vi/LC_MESSAGES') recursedown('./django/conf/locale/zh_Hans') recursedown('./django/conf/locale/zh_Hans/LC_MESSAGES') recursedown('./django/conf/locale/zh_Hant') recursedown('./django/conf/locale/zh_Hant/LC_MESSAGES') recursedown('./django/conf/project_template') recursedown('./django/conf/project_template/project_name') recursedown('./django/conf/urls') recursedown('./django/contrib') recursedown('./django/contrib/admin') recursedown('./django/contrib/admin/locale') recursedown('./django/contrib/admin/locale/af') recursedown('./django/contrib/admin/locale/af/LC_MESSAGES') recursedown('./django/contrib/admin/locale/am') recursedown('./django/contrib/admin/locale/am/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ar') recursedown('./django/contrib/admin/locale/ar/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ar_DZ') recursedown('./django/contrib/admin/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ast') recursedown('./django/contrib/admin/locale/ast/LC_MESSAGES') recursedown('./django/contrib/admin/locale/az') recursedown('./django/contrib/admin/locale/az/LC_MESSAGES') recursedown('./django/contrib/admin/locale/be') recursedown('./django/contrib/admin/locale/be/LC_MESSAGES') recursedown('./django/contrib/admin/locale/bg') recursedown('./django/contrib/admin/locale/bg/LC_MESSAGES') recursedown('./django/contrib/admin/locale/bn') recursedown('./django/contrib/admin/locale/bn/LC_MESSAGES') recursedown('./django/contrib/admin/locale/br') recursedown('./django/contrib/admin/locale/br/LC_MESSAGES') recursedown('./django/contrib/admin/locale/bs') recursedown('./django/contrib/admin/locale/bs/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ca') recursedown('./django/contrib/admin/locale/ca/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ckb') recursedown('./django/contrib/admin/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/admin/locale/cs') recursedown('./django/contrib/admin/locale/cs/LC_MESSAGES') recursedown('./django/contrib/admin/locale/cy') recursedown('./django/contrib/admin/locale/cy/LC_MESSAGES') recursedown('./django/contrib/admin/locale/da') recursedown('./django/contrib/admin/locale/da/LC_MESSAGES') recursedown('./django/contrib/admin/locale/de') recursedown('./django/contrib/admin/locale/de/LC_MESSAGES') recursedown('./django/contrib/admin/locale/dsb') recursedown('./django/contrib/admin/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/admin/locale/el') recursedown('./django/contrib/admin/locale/el/LC_MESSAGES') recursedown('./django/contrib/admin/locale/en') recursedown('./django/contrib/admin/locale/en/LC_MESSAGES') recursedown('./django/contrib/admin/locale/en_AU') recursedown('./django/contrib/admin/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/admin/locale/en_GB') recursedown('./django/contrib/admin/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/admin/locale/eo') recursedown('./django/contrib/admin/locale/eo/LC_MESSAGES') recursedown('./django/contrib/admin/locale/es') recursedown('./django/contrib/admin/locale/es/LC_MESSAGES') recursedown('./django/contrib/admin/locale/es_AR') recursedown('./django/contrib/admin/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/admin/locale/es_CO') recursedown('./django/contrib/admin/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/admin/locale/es_MX') recursedown('./django/contrib/admin/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/admin/locale/es_VE') recursedown('./django/contrib/admin/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/admin/locale/et') recursedown('./django/contrib/admin/locale/et/LC_MESSAGES') recursedown('./django/contrib/admin/locale/eu') recursedown('./django/contrib/admin/locale/eu/LC_MESSAGES') recursedown('./django/contrib/admin/locale/fa') recursedown('./django/contrib/admin/locale/fa/LC_MESSAGES') recursedown('./django/contrib/admin/locale/fi') recursedown('./django/contrib/admin/locale/fi/LC_MESSAGES') recursedown('./django/contrib/admin/locale/fr') recursedown('./django/contrib/admin/locale/fr/LC_MESSAGES') recursedown('./django/contrib/admin/locale/fy') recursedown('./django/contrib/admin/locale/fy/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ga') recursedown('./django/contrib/admin/locale/ga/LC_MESSAGES') recursedown('./django/contrib/admin/locale/gd') recursedown('./django/contrib/admin/locale/gd/LC_MESSAGES') recursedown('./django/contrib/admin/locale/gl') recursedown('./django/contrib/admin/locale/gl/LC_MESSAGES') recursedown('./django/contrib/admin/locale/he') recursedown('./django/contrib/admin/locale/he/LC_MESSAGES') recursedown('./django/contrib/admin/locale/hi') recursedown('./django/contrib/admin/locale/hi/LC_MESSAGES') recursedown('./django/contrib/admin/locale/hr') recursedown('./django/contrib/admin/locale/hr/LC_MESSAGES') recursedown('./django/contrib/admin/locale/hsb') recursedown('./django/contrib/admin/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/admin/locale/hu') recursedown('./django/contrib/admin/locale/hu/LC_MESSAGES') recursedown('./django/contrib/admin/locale/hy') recursedown('./django/contrib/admin/locale/hy/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ia') recursedown('./django/contrib/admin/locale/ia/LC_MESSAGES') recursedown('./django/contrib/admin/locale/id') recursedown('./django/contrib/admin/locale/id/LC_MESSAGES') recursedown('./django/contrib/admin/locale/io') recursedown('./django/contrib/admin/locale/io/LC_MESSAGES') recursedown('./django/contrib/admin/locale/is') recursedown('./django/contrib/admin/locale/is/LC_MESSAGES') recursedown('./django/contrib/admin/locale/it') recursedown('./django/contrib/admin/locale/it/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ja') recursedown('./django/contrib/admin/locale/ja/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ka') recursedown('./django/contrib/admin/locale/ka/LC_MESSAGES') recursedown('./django/contrib/admin/locale/kab') recursedown('./django/contrib/admin/locale/kab/LC_MESSAGES') recursedown('./django/contrib/admin/locale/kk') recursedown('./django/contrib/admin/locale/kk/LC_MESSAGES') recursedown('./django/contrib/admin/locale/km') recursedown('./django/contrib/admin/locale/km/LC_MESSAGES') recursedown('./django/contrib/admin/locale/kn') recursedown('./django/contrib/admin/locale/kn/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ko') recursedown('./django/contrib/admin/locale/ko/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ky') recursedown('./django/contrib/admin/locale/ky/LC_MESSAGES') recursedown('./django/contrib/admin/locale/lb') recursedown('./django/contrib/admin/locale/lb/LC_MESSAGES') recursedown('./django/contrib/admin/locale/lt') recursedown('./django/contrib/admin/locale/lt/LC_MESSAGES') recursedown('./django/contrib/admin/locale/lv') recursedown('./django/contrib/admin/locale/lv/LC_MESSAGES') recursedown('./django/contrib/admin/locale/mk') recursedown('./django/contrib/admin/locale/mk/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ml') recursedown('./django/contrib/admin/locale/ml/LC_MESSAGES') recursedown('./django/contrib/admin/locale/mn') recursedown('./django/contrib/admin/locale/mn/LC_MESSAGES') recursedown('./django/contrib/admin/locale/mr') recursedown('./django/contrib/admin/locale/mr/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ms') recursedown('./django/contrib/admin/locale/ms/LC_MESSAGES') recursedown('./django/contrib/admin/locale/my') recursedown('./django/contrib/admin/locale/my/LC_MESSAGES') recursedown('./django/contrib/admin/locale/nb') recursedown('./django/contrib/admin/locale/nb/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ne') recursedown('./django/contrib/admin/locale/ne/LC_MESSAGES') recursedown('./django/contrib/admin/locale/nl') recursedown('./django/contrib/admin/locale/nl/LC_MESSAGES') recursedown('./django/contrib/admin/locale/nn') recursedown('./django/contrib/admin/locale/nn/LC_MESSAGES') recursedown('./django/contrib/admin/locale/os') recursedown('./django/contrib/admin/locale/os/LC_MESSAGES') recursedown('./django/contrib/admin/locale/pa') recursedown('./django/contrib/admin/locale/pa/LC_MESSAGES') recursedown('./django/contrib/admin/locale/pl') recursedown('./django/contrib/admin/locale/pl/LC_MESSAGES') recursedown('./django/contrib/admin/locale/pt') recursedown('./django/contrib/admin/locale/pt/LC_MESSAGES') recursedown('./django/contrib/admin/locale/pt_BR') recursedown('./django/contrib/admin/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ro') recursedown('./django/contrib/admin/locale/ro/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ru') recursedown('./django/contrib/admin/locale/ru/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sk') recursedown('./django/contrib/admin/locale/sk/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sl') recursedown('./django/contrib/admin/locale/sl/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sq') recursedown('./django/contrib/admin/locale/sq/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sr') recursedown('./django/contrib/admin/locale/sr/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sr_Latn') recursedown('./django/contrib/admin/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sv') recursedown('./django/contrib/admin/locale/sv/LC_MESSAGES') recursedown('./django/contrib/admin/locale/sw') recursedown('./django/contrib/admin/locale/sw/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ta') recursedown('./django/contrib/admin/locale/ta/LC_MESSAGES') recursedown('./django/contrib/admin/locale/te') recursedown('./django/contrib/admin/locale/te/LC_MESSAGES') recursedown('./django/contrib/admin/locale/tg') recursedown('./django/contrib/admin/locale/tg/LC_MESSAGES') recursedown('./django/contrib/admin/locale/th') recursedown('./django/contrib/admin/locale/th/LC_MESSAGES') recursedown('./django/contrib/admin/locale/tk') recursedown('./django/contrib/admin/locale/tk/LC_MESSAGES') recursedown('./django/contrib/admin/locale/tr') recursedown('./django/contrib/admin/locale/tr/LC_MESSAGES') recursedown('./django/contrib/admin/locale/tt') recursedown('./django/contrib/admin/locale/tt/LC_MESSAGES') recursedown('./django/contrib/admin/locale/udm') recursedown('./django/contrib/admin/locale/udm/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ug') recursedown('./django/contrib/admin/locale/ug/LC_MESSAGES') recursedown('./django/contrib/admin/locale/uk') recursedown('./django/contrib/admin/locale/uk/LC_MESSAGES') recursedown('./django/contrib/admin/locale/ur') recursedown('./django/contrib/admin/locale/ur/LC_MESSAGES') recursedown('./django/contrib/admin/locale/uz') recursedown('./django/contrib/admin/locale/uz/LC_MESSAGES') recursedown('./django/contrib/admin/locale/vi') recursedown('./django/contrib/admin/locale/vi/LC_MESSAGES') recursedown('./django/contrib/admin/locale/zh_Hans') recursedown('./django/contrib/admin/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/admin/locale/zh_Hant') recursedown('./django/contrib/admin/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/admin/migrations') recursedown('./django/contrib/admin/static') recursedown('./django/contrib/admin/static/admin') recursedown('./django/contrib/admin/static/admin/css') recursedown('./django/contrib/admin/static/admin/css/vendor') recursedown('./django/contrib/admin/static/admin/css/vendor/select2') recursedown('./django/contrib/admin/static/admin/img') recursedown('./django/contrib/admin/static/admin/img/gis') recursedown('./django/contrib/admin/static/admin/js') recursedown('./django/contrib/admin/static/admin/js/admin') recursedown('./django/contrib/admin/static/admin/js/vendor') recursedown('./django/contrib/admin/static/admin/js/vendor/jquery') recursedown('./django/contrib/admin/static/admin/js/vendor/select2') recursedown('./django/contrib/admin/static/admin/js/vendor/select2/i18n') recursedown('./django/contrib/admin/static/admin/js/vendor/xregexp') recursedown('./django/contrib/admin/templates') recursedown('./django/contrib/admin/templates/admin') recursedown('./django/contrib/admin/templates/admin/auth') recursedown('./django/contrib/admin/templates/admin/auth/user') recursedown('./django/contrib/admin/templates/admin/edit_inline') recursedown('./django/contrib/admin/templates/admin/includes') recursedown('./django/contrib/admin/templates/admin/widgets') recursedown('./django/contrib/admin/templates/registration') recursedown('./django/contrib/admin/templatetags') recursedown('./django/contrib/admin/views') recursedown('./django/contrib/admindocs') recursedown('./django/contrib/admindocs/locale') recursedown('./django/contrib/admindocs/locale/af') recursedown('./django/contrib/admindocs/locale/af/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ar') recursedown('./django/contrib/admindocs/locale/ar/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ar_DZ') recursedown('./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ast') recursedown('./django/contrib/admindocs/locale/ast/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/az') recursedown('./django/contrib/admindocs/locale/az/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/be') recursedown('./django/contrib/admindocs/locale/be/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/bg') recursedown('./django/contrib/admindocs/locale/bg/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/bn') recursedown('./django/contrib/admindocs/locale/bn/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/br') recursedown('./django/contrib/admindocs/locale/br/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/bs') recursedown('./django/contrib/admindocs/locale/bs/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ca') recursedown('./django/contrib/admindocs/locale/ca/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ckb') recursedown('./django/contrib/admindocs/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/cs') recursedown('./django/contrib/admindocs/locale/cs/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/cy') recursedown('./django/contrib/admindocs/locale/cy/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/da') recursedown('./django/contrib/admindocs/locale/da/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/de') recursedown('./django/contrib/admindocs/locale/de/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/dsb') recursedown('./django/contrib/admindocs/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/el') recursedown('./django/contrib/admindocs/locale/el/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/en') recursedown('./django/contrib/admindocs/locale/en/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/en_AU') recursedown('./django/contrib/admindocs/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/en_GB') recursedown('./django/contrib/admindocs/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/eo') recursedown('./django/contrib/admindocs/locale/eo/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/es') recursedown('./django/contrib/admindocs/locale/es/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/es_AR') recursedown('./django/contrib/admindocs/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/es_CO') recursedown('./django/contrib/admindocs/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/es_MX') recursedown('./django/contrib/admindocs/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/es_VE') recursedown('./django/contrib/admindocs/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/et') recursedown('./django/contrib/admindocs/locale/et/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/eu') recursedown('./django/contrib/admindocs/locale/eu/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/fa') recursedown('./django/contrib/admindocs/locale/fa/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/fi') recursedown('./django/contrib/admindocs/locale/fi/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/fr') recursedown('./django/contrib/admindocs/locale/fr/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/fy') recursedown('./django/contrib/admindocs/locale/fy/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ga') recursedown('./django/contrib/admindocs/locale/ga/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/gd') recursedown('./django/contrib/admindocs/locale/gd/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/gl') recursedown('./django/contrib/admindocs/locale/gl/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/he') recursedown('./django/contrib/admindocs/locale/he/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/hi') recursedown('./django/contrib/admindocs/locale/hi/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/hr') recursedown('./django/contrib/admindocs/locale/hr/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/hsb') recursedown('./django/contrib/admindocs/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/hu') recursedown('./django/contrib/admindocs/locale/hu/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ia') recursedown('./django/contrib/admindocs/locale/ia/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/id') recursedown('./django/contrib/admindocs/locale/id/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/io') recursedown('./django/contrib/admindocs/locale/io/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/is') recursedown('./django/contrib/admindocs/locale/is/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/it') recursedown('./django/contrib/admindocs/locale/it/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ja') recursedown('./django/contrib/admindocs/locale/ja/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ka') recursedown('./django/contrib/admindocs/locale/ka/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/kab') recursedown('./django/contrib/admindocs/locale/kab/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/kk') recursedown('./django/contrib/admindocs/locale/kk/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/km') recursedown('./django/contrib/admindocs/locale/km/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/kn') recursedown('./django/contrib/admindocs/locale/kn/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ko') recursedown('./django/contrib/admindocs/locale/ko/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ky') recursedown('./django/contrib/admindocs/locale/ky/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/lb') recursedown('./django/contrib/admindocs/locale/lb/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/lt') recursedown('./django/contrib/admindocs/locale/lt/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/lv') recursedown('./django/contrib/admindocs/locale/lv/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/mk') recursedown('./django/contrib/admindocs/locale/mk/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ml') recursedown('./django/contrib/admindocs/locale/ml/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/mn') recursedown('./django/contrib/admindocs/locale/mn/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/mr') recursedown('./django/contrib/admindocs/locale/mr/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ms') recursedown('./django/contrib/admindocs/locale/ms/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/my') recursedown('./django/contrib/admindocs/locale/my/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/nb') recursedown('./django/contrib/admindocs/locale/nb/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ne') recursedown('./django/contrib/admindocs/locale/ne/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/nl') recursedown('./django/contrib/admindocs/locale/nl/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/nn') recursedown('./django/contrib/admindocs/locale/nn/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/os') recursedown('./django/contrib/admindocs/locale/os/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/pa') recursedown('./django/contrib/admindocs/locale/pa/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/pl') recursedown('./django/contrib/admindocs/locale/pl/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/pt') recursedown('./django/contrib/admindocs/locale/pt/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/pt_BR') recursedown('./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ro') recursedown('./django/contrib/admindocs/locale/ro/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ru') recursedown('./django/contrib/admindocs/locale/ru/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sk') recursedown('./django/contrib/admindocs/locale/sk/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sl') recursedown('./django/contrib/admindocs/locale/sl/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sq') recursedown('./django/contrib/admindocs/locale/sq/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sr') recursedown('./django/contrib/admindocs/locale/sr/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sr_Latn') recursedown('./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sv') recursedown('./django/contrib/admindocs/locale/sv/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/sw') recursedown('./django/contrib/admindocs/locale/sw/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ta') recursedown('./django/contrib/admindocs/locale/ta/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/te') recursedown('./django/contrib/admindocs/locale/te/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/tg') recursedown('./django/contrib/admindocs/locale/tg/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/th') recursedown('./django/contrib/admindocs/locale/th/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/tr') recursedown('./django/contrib/admindocs/locale/tr/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/tt') recursedown('./django/contrib/admindocs/locale/tt/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/udm') recursedown('./django/contrib/admindocs/locale/udm/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ug') recursedown('./django/contrib/admindocs/locale/ug/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/uk') recursedown('./django/contrib/admindocs/locale/uk/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/ur') recursedown('./django/contrib/admindocs/locale/ur/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/vi') recursedown('./django/contrib/admindocs/locale/vi/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/zh_Hans') recursedown('./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/admindocs/locale/zh_Hant') recursedown('./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/admindocs/templates') recursedown('./django/contrib/admindocs/templates/admin_doc') recursedown('./django/contrib/auth') recursedown('./django/contrib/auth/handlers') recursedown('./django/contrib/auth/locale') recursedown('./django/contrib/auth/locale/af') recursedown('./django/contrib/auth/locale/af/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ar') recursedown('./django/contrib/auth/locale/ar/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ar_DZ') recursedown('./django/contrib/auth/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ast') recursedown('./django/contrib/auth/locale/ast/LC_MESSAGES') recursedown('./django/contrib/auth/locale/az') recursedown('./django/contrib/auth/locale/az/LC_MESSAGES') recursedown('./django/contrib/auth/locale/be') recursedown('./django/contrib/auth/locale/be/LC_MESSAGES') recursedown('./django/contrib/auth/locale/bg') recursedown('./django/contrib/auth/locale/bg/LC_MESSAGES') recursedown('./django/contrib/auth/locale/bn') recursedown('./django/contrib/auth/locale/bn/LC_MESSAGES') recursedown('./django/contrib/auth/locale/br') recursedown('./django/contrib/auth/locale/br/LC_MESSAGES') recursedown('./django/contrib/auth/locale/bs') recursedown('./django/contrib/auth/locale/bs/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ca') recursedown('./django/contrib/auth/locale/ca/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ckb') recursedown('./django/contrib/auth/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/auth/locale/cs') recursedown('./django/contrib/auth/locale/cs/LC_MESSAGES') recursedown('./django/contrib/auth/locale/cy') recursedown('./django/contrib/auth/locale/cy/LC_MESSAGES') recursedown('./django/contrib/auth/locale/da') recursedown('./django/contrib/auth/locale/da/LC_MESSAGES') recursedown('./django/contrib/auth/locale/de') recursedown('./django/contrib/auth/locale/de/LC_MESSAGES') recursedown('./django/contrib/auth/locale/dsb') recursedown('./django/contrib/auth/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/auth/locale/el') recursedown('./django/contrib/auth/locale/el/LC_MESSAGES') recursedown('./django/contrib/auth/locale/en') recursedown('./django/contrib/auth/locale/en/LC_MESSAGES') recursedown('./django/contrib/auth/locale/en_AU') recursedown('./django/contrib/auth/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/auth/locale/en_GB') recursedown('./django/contrib/auth/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/auth/locale/eo') recursedown('./django/contrib/auth/locale/eo/LC_MESSAGES') recursedown('./django/contrib/auth/locale/es') recursedown('./django/contrib/auth/locale/es/LC_MESSAGES') recursedown('./django/contrib/auth/locale/es_AR') recursedown('./django/contrib/auth/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/auth/locale/es_CO') recursedown('./django/contrib/auth/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/auth/locale/es_MX') recursedown('./django/contrib/auth/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/auth/locale/es_VE') recursedown('./django/contrib/auth/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/auth/locale/et') recursedown('./django/contrib/auth/locale/et/LC_MESSAGES') recursedown('./django/contrib/auth/locale/eu') recursedown('./django/contrib/auth/locale/eu/LC_MESSAGES') recursedown('./django/contrib/auth/locale/fa') recursedown('./django/contrib/auth/locale/fa/LC_MESSAGES') recursedown('./django/contrib/auth/locale/fi') recursedown('./django/contrib/auth/locale/fi/LC_MESSAGES') recursedown('./django/contrib/auth/locale/fr') recursedown('./django/contrib/auth/locale/fr/LC_MESSAGES') recursedown('./django/contrib/auth/locale/fy') recursedown('./django/contrib/auth/locale/fy/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ga') recursedown('./django/contrib/auth/locale/ga/LC_MESSAGES') recursedown('./django/contrib/auth/locale/gd') recursedown('./django/contrib/auth/locale/gd/LC_MESSAGES') recursedown('./django/contrib/auth/locale/gl') recursedown('./django/contrib/auth/locale/gl/LC_MESSAGES') recursedown('./django/contrib/auth/locale/he') recursedown('./django/contrib/auth/locale/he/LC_MESSAGES') recursedown('./django/contrib/auth/locale/hi') recursedown('./django/contrib/auth/locale/hi/LC_MESSAGES') recursedown('./django/contrib/auth/locale/hr') recursedown('./django/contrib/auth/locale/hr/LC_MESSAGES') recursedown('./django/contrib/auth/locale/hsb') recursedown('./django/contrib/auth/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/auth/locale/hu') recursedown('./django/contrib/auth/locale/hu/LC_MESSAGES') recursedown('./django/contrib/auth/locale/hy') recursedown('./django/contrib/auth/locale/hy/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ia') recursedown('./django/contrib/auth/locale/ia/LC_MESSAGES') recursedown('./django/contrib/auth/locale/id') recursedown('./django/contrib/auth/locale/id/LC_MESSAGES') recursedown('./django/contrib/auth/locale/io') recursedown('./django/contrib/auth/locale/io/LC_MESSAGES') recursedown('./django/contrib/auth/locale/is') recursedown('./django/contrib/auth/locale/is/LC_MESSAGES') recursedown('./django/contrib/auth/locale/it') recursedown('./django/contrib/auth/locale/it/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ja') recursedown('./django/contrib/auth/locale/ja/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ka') recursedown('./django/contrib/auth/locale/ka/LC_MESSAGES') recursedown('./django/contrib/auth/locale/kab') recursedown('./django/contrib/auth/locale/kab/LC_MESSAGES') recursedown('./django/contrib/auth/locale/kk') recursedown('./django/contrib/auth/locale/kk/LC_MESSAGES') recursedown('./django/contrib/auth/locale/km') recursedown('./django/contrib/auth/locale/km/LC_MESSAGES') recursedown('./django/contrib/auth/locale/kn') recursedown('./django/contrib/auth/locale/kn/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ko') recursedown('./django/contrib/auth/locale/ko/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ky') recursedown('./django/contrib/auth/locale/ky/LC_MESSAGES') recursedown('./django/contrib/auth/locale/lb') recursedown('./django/contrib/auth/locale/lb/LC_MESSAGES') recursedown('./django/contrib/auth/locale/lt') recursedown('./django/contrib/auth/locale/lt/LC_MESSAGES') recursedown('./django/contrib/auth/locale/lv') recursedown('./django/contrib/auth/locale/lv/LC_MESSAGES') recursedown('./django/contrib/auth/locale/mk') recursedown('./django/contrib/auth/locale/mk/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ml') recursedown('./django/contrib/auth/locale/ml/LC_MESSAGES') recursedown('./django/contrib/auth/locale/mn') recursedown('./django/contrib/auth/locale/mn/LC_MESSAGES') recursedown('./django/contrib/auth/locale/mr') recursedown('./django/contrib/auth/locale/mr/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ms') recursedown('./django/contrib/auth/locale/ms/LC_MESSAGES') recursedown('./django/contrib/auth/locale/my') recursedown('./django/contrib/auth/locale/my/LC_MESSAGES') recursedown('./django/contrib/auth/locale/nb') recursedown('./django/contrib/auth/locale/nb/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ne') recursedown('./django/contrib/auth/locale/ne/LC_MESSAGES') recursedown('./django/contrib/auth/locale/nl') recursedown('./django/contrib/auth/locale/nl/LC_MESSAGES') recursedown('./django/contrib/auth/locale/nn') recursedown('./django/contrib/auth/locale/nn/LC_MESSAGES') recursedown('./django/contrib/auth/locale/os') recursedown('./django/contrib/auth/locale/os/LC_MESSAGES') recursedown('./django/contrib/auth/locale/pa') recursedown('./django/contrib/auth/locale/pa/LC_MESSAGES') recursedown('./django/contrib/auth/locale/pl') recursedown('./django/contrib/auth/locale/pl/LC_MESSAGES') recursedown('./django/contrib/auth/locale/pt') recursedown('./django/contrib/auth/locale/pt/LC_MESSAGES') recursedown('./django/contrib/auth/locale/pt_BR') recursedown('./django/contrib/auth/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ro') recursedown('./django/contrib/auth/locale/ro/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ru') recursedown('./django/contrib/auth/locale/ru/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sk') recursedown('./django/contrib/auth/locale/sk/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sl') recursedown('./django/contrib/auth/locale/sl/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sq') recursedown('./django/contrib/auth/locale/sq/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sr') recursedown('./django/contrib/auth/locale/sr/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sr_Latn') recursedown('./django/contrib/auth/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sv') recursedown('./django/contrib/auth/locale/sv/LC_MESSAGES') recursedown('./django/contrib/auth/locale/sw') recursedown('./django/contrib/auth/locale/sw/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ta') recursedown('./django/contrib/auth/locale/ta/LC_MESSAGES') recursedown('./django/contrib/auth/locale/te') recursedown('./django/contrib/auth/locale/te/LC_MESSAGES') recursedown('./django/contrib/auth/locale/tg') recursedown('./django/contrib/auth/locale/tg/LC_MESSAGES') recursedown('./django/contrib/auth/locale/th') recursedown('./django/contrib/auth/locale/th/LC_MESSAGES') recursedown('./django/contrib/auth/locale/tk') recursedown('./django/contrib/auth/locale/tk/LC_MESSAGES') recursedown('./django/contrib/auth/locale/tr') recursedown('./django/contrib/auth/locale/tr/LC_MESSAGES') recursedown('./django/contrib/auth/locale/tt') recursedown('./django/contrib/auth/locale/tt/LC_MESSAGES') recursedown('./django/contrib/auth/locale/udm') recursedown('./django/contrib/auth/locale/udm/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ug') recursedown('./django/contrib/auth/locale/ug/LC_MESSAGES') recursedown('./django/contrib/auth/locale/uk') recursedown('./django/contrib/auth/locale/uk/LC_MESSAGES') recursedown('./django/contrib/auth/locale/ur') recursedown('./django/contrib/auth/locale/ur/LC_MESSAGES') recursedown('./django/contrib/auth/locale/uz') recursedown('./django/contrib/auth/locale/uz/LC_MESSAGES') recursedown('./django/contrib/auth/locale/vi') recursedown('./django/contrib/auth/locale/vi/LC_MESSAGES') recursedown('./django/contrib/auth/locale/zh_Hans') recursedown('./django/contrib/auth/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/auth/locale/zh_Hant') recursedown('./django/contrib/auth/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/auth/management') recursedown('./django/contrib/auth/management/commands') recursedown('./django/contrib/auth/migrations') recursedown('./django/contrib/auth/templates') recursedown('./django/contrib/auth/templates/auth') recursedown('./django/contrib/auth/templates/auth/widgets') recursedown('./django/contrib/auth/templates/registration') recursedown('./django/contrib/contenttypes') recursedown('./django/contrib/contenttypes/locale') recursedown('./django/contrib/contenttypes/locale/af') recursedown('./django/contrib/contenttypes/locale/af/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ar') recursedown('./django/contrib/contenttypes/locale/ar/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ar_DZ') recursedown('./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ast') recursedown('./django/contrib/contenttypes/locale/ast/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/az') recursedown('./django/contrib/contenttypes/locale/az/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/be') recursedown('./django/contrib/contenttypes/locale/be/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/bg') recursedown('./django/contrib/contenttypes/locale/bg/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/bn') recursedown('./django/contrib/contenttypes/locale/bn/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/br') recursedown('./django/contrib/contenttypes/locale/br/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/bs') recursedown('./django/contrib/contenttypes/locale/bs/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ca') recursedown('./django/contrib/contenttypes/locale/ca/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ckb') recursedown('./django/contrib/contenttypes/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/cs') recursedown('./django/contrib/contenttypes/locale/cs/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/cy') recursedown('./django/contrib/contenttypes/locale/cy/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/da') recursedown('./django/contrib/contenttypes/locale/da/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/de') recursedown('./django/contrib/contenttypes/locale/de/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/dsb') recursedown('./django/contrib/contenttypes/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/el') recursedown('./django/contrib/contenttypes/locale/el/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/en') recursedown('./django/contrib/contenttypes/locale/en/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/en_AU') recursedown('./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/en_GB') recursedown('./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/eo') recursedown('./django/contrib/contenttypes/locale/eo/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/es') recursedown('./django/contrib/contenttypes/locale/es/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/es_AR') recursedown('./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/es_CO') recursedown('./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/es_MX') recursedown('./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/es_VE') recursedown('./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/et') recursedown('./django/contrib/contenttypes/locale/et/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/eu') recursedown('./django/contrib/contenttypes/locale/eu/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/fa') recursedown('./django/contrib/contenttypes/locale/fa/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/fi') recursedown('./django/contrib/contenttypes/locale/fi/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/fr') recursedown('./django/contrib/contenttypes/locale/fr/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/fy') recursedown('./django/contrib/contenttypes/locale/fy/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ga') recursedown('./django/contrib/contenttypes/locale/ga/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/gd') recursedown('./django/contrib/contenttypes/locale/gd/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/gl') recursedown('./django/contrib/contenttypes/locale/gl/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/he') recursedown('./django/contrib/contenttypes/locale/he/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/hi') recursedown('./django/contrib/contenttypes/locale/hi/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/hr') recursedown('./django/contrib/contenttypes/locale/hr/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/hsb') recursedown('./django/contrib/contenttypes/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/hu') recursedown('./django/contrib/contenttypes/locale/hu/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/hy') recursedown('./django/contrib/contenttypes/locale/hy/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ia') recursedown('./django/contrib/contenttypes/locale/ia/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/id') recursedown('./django/contrib/contenttypes/locale/id/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/io') recursedown('./django/contrib/contenttypes/locale/io/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/is') recursedown('./django/contrib/contenttypes/locale/is/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/it') recursedown('./django/contrib/contenttypes/locale/it/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ja') recursedown('./django/contrib/contenttypes/locale/ja/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ka') recursedown('./django/contrib/contenttypes/locale/ka/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/kk') recursedown('./django/contrib/contenttypes/locale/kk/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/km') recursedown('./django/contrib/contenttypes/locale/km/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/kn') recursedown('./django/contrib/contenttypes/locale/kn/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ko') recursedown('./django/contrib/contenttypes/locale/ko/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ky') recursedown('./django/contrib/contenttypes/locale/ky/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/lb') recursedown('./django/contrib/contenttypes/locale/lb/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/lt') recursedown('./django/contrib/contenttypes/locale/lt/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/lv') recursedown('./django/contrib/contenttypes/locale/lv/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/mk') recursedown('./django/contrib/contenttypes/locale/mk/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ml') recursedown('./django/contrib/contenttypes/locale/ml/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/mn') recursedown('./django/contrib/contenttypes/locale/mn/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/mr') recursedown('./django/contrib/contenttypes/locale/mr/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ms') recursedown('./django/contrib/contenttypes/locale/ms/LC_MESSAGES') ./django/conf/urls/__init__.py: no change ./django/conf/urls/i18n.py: no change ./django/conf/urls/static.py: no change ./django/contrib/__init__.py: no change ./django/contrib/admin/__init__.py: no change ./django/contrib/admin/actions.py: no change ./django/contrib/admin/apps.py: no change ./django/contrib/admin/checks.py: no change ./django/contrib/admin/decorators.py: no change ./django/contrib/admin/exceptions.py: no change ./django/contrib/admin/filters.py: no change ./django/contrib/admin/forms.py: no change ./django/contrib/admin/helpers.py: no change ./django/contrib/admin/models.py: no change ./django/contrib/admin/options.py: no change ./django/contrib/admin/sites.py: no change ./django/contrib/admin/tests.py: no change ./django/contrib/admin/utils.py: no change ./django/contrib/admin/widgets.py: no change ./django/contrib/admin/migrations/0001_initial.py: no change ./django/contrib/admin/migrations/0002_logentry_remove_auto_add.py: no change ./django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py: no change ./django/contrib/admin/migrations/__init__.py: no change ./django/contrib/admin/templatetags/__init__.py: no change ./django/contrib/admin/templatetags/admin_list.py: no change ./django/contrib/admin/templatetags/admin_modify.py: no change ./django/contrib/admin/templatetags/admin_urls.py: no change ./django/contrib/admin/templatetags/base.py: no change ./django/contrib/admin/templatetags/log.py: no change ./django/contrib/admin/views/__init__.py: no change ./django/contrib/admin/views/autocomplete.py: no change ./django/contrib/admin/views/decorators.py: no change ./django/contrib/admin/views/main.py: no change ./django/contrib/admindocs/__init__.py: no change ./django/contrib/admindocs/apps.py: no change ./django/contrib/admindocs/middleware.py: no change ./django/contrib/admindocs/urls.py: no change ./django/contrib/admindocs/utils.py: no change ./django/contrib/admindocs/views.py: no change ./django/contrib/auth/__init__.py: no change ./django/contrib/auth/admin.py: no change ./django/contrib/auth/apps.py: no change ./django/contrib/auth/backends.py: no change ./django/contrib/auth/base_user.py: no change ./django/contrib/auth/checks.py: no change ./django/contrib/auth/context_processors.py: no change ./django/contrib/auth/decorators.py: no change ./django/contrib/auth/forms.py: no change ./django/contrib/auth/hashers.py: no change ./django/contrib/auth/middleware.py: no change ./django/contrib/auth/mixins.py: no change ./django/contrib/auth/models.py: no change ./django/contrib/auth/password_validation.py: no change ./django/contrib/auth/signals.py: no change ./django/contrib/auth/tokens.py: no change ./django/contrib/auth/urls.py: no change ./django/contrib/auth/validators.py: no change ./django/contrib/auth/views.py: no change ./django/contrib/auth/handlers/__init__.py: no change ./django/contrib/auth/handlers/modwsgi.py: no change ./django/contrib/auth/management/__init__.py: no change ./django/contrib/auth/management/commands/__init__.py: no change ./django/contrib/auth/management/commands/changepassword.py: no change ./django/contrib/auth/management/commands/createsuperuser.py: no change ./django/contrib/auth/migrations/0001_initial.py: no change ./django/contrib/auth/migrations/0002_alter_permission_name_max_length.py: no change ./django/contrib/auth/migrations/0003_alter_user_email_max_length.py: no change ./django/contrib/auth/migrations/0004_alter_user_username_opts.py: no change ./django/contrib/auth/migrations/0005_alter_user_last_login_null.py: no change ./django/contrib/auth/migrations/0006_require_contenttypes_0002.py: no change ./django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py: no change ./django/contrib/auth/migrations/0008_alter_user_username_max_length.py: no change ./django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py: no change ./django/contrib/auth/migrations/0010_alter_group_name_max_length.py: no change ./django/contrib/auth/migrations/0011_update_proxy_permissions.py: no change ./django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py: no change ./django/contrib/auth/migrations/__init__.py: no change ./django/contrib/contenttypes/__init__.py: no change ./django/contrib/contenttypes/admin.py: no change ./django/contrib/contenttypes/apps.py: no change ./django/contrib/contenttypes/checks.py: no change ./django/contrib/contenttypes/fields.py: no change ./django/contrib/contenttypes/forms.py: no change ./django/contrib/contenttypes/models.py: no change ./django/contrib/contenttypes/prefetch.py: no change ./django/contrib/contenttypes/views.py: no change ./django/contrib/contenttypes/management/__init__.py: no change ./django/contrib/contenttypes/management/commands/__init__.py: no change ./django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py: no change ./django/contrib/contenttypes/migrations/0001_initial.py: no change ./django/contrib/contenttypes/migrations/0002_remove_content_type_name.py: no change ./django/contrib/contenttypes/migrations/__init__.py: no change ./django/contrib/flatpages/__init__.py: no change ./django/contrib/flatpages/admin.py: no change ./django/contrib/flatpages/apps.py: no change ./django/contrib/flatpages/forms.py: no change ./django/contrib/flatpages/middleware.py: no change ./django/contrib/flatpages/models.py: no change ./django/contrib/flatpages/sitemaps.py: no change ./django/contrib/flatpages/urls.py: no change ./django/contrib/flatpages/views.py: no change ./django/contrib/flatpages/migrations/0001_initial.py: no change ./django/contrib/flatpages/migrations/__init__.py: no change ./django/contrib/flatpages/templatetags/__init__.py: no change ./django/contrib/flatpages/templatetags/flatpages.py: no change ./django/contrib/gis/__init__.py: no change ./django/contrib/gis/apps.py: no change ./django/contrib/gis/feeds.py: no change ./django/contrib/gis/geometry.py: no change ./django/contrib/gis/measure.py: no change ./django/contrib/gis/ptr.py: no change ./django/contrib/gis/shortcuts.py: no change ./django/contrib/gis/views.py: no change ./django/contrib/gis/admin/__init__.py: no change ./django/contrib/gis/admin/options.py: no change ./django/contrib/gis/db/__init__.py: no change ./django/contrib/gis/db/backends/__init__.py: no change ./django/contrib/gis/db/backends/utils.py: no change ./django/contrib/gis/db/backends/base/__init__.py: no change ./django/contrib/gis/db/backends/base/adapter.py: no change ./django/contrib/gis/db/backends/base/features.py: no change ./django/contrib/gis/db/backends/base/models.py: no change ./django/contrib/gis/db/backends/base/operations.py: no change ./django/contrib/gis/db/backends/mysql/__init__.py: no change ./django/contrib/gis/db/backends/mysql/base.py: no change ./django/contrib/gis/db/backends/mysql/features.py: no change ./django/contrib/gis/db/backends/mysql/introspection.py: no change ./django/contrib/gis/db/backends/mysql/operations.py: no change ./django/contrib/gis/db/backends/mysql/schema.py: no change ./django/contrib/gis/db/backends/oracle/__init__.py: no change ./django/contrib/gis/db/backends/oracle/adapter.py: no change ./django/contrib/gis/db/backends/oracle/base.py: no change ./django/contrib/gis/db/backends/oracle/features.py: no change ./django/contrib/gis/db/backends/oracle/introspection.py: no change ./django/contrib/gis/db/backends/oracle/models.py: no change ./django/contrib/gis/db/backends/oracle/operations.py: no change ./django/contrib/gis/db/backends/oracle/schema.py: no change ./django/contrib/gis/db/backends/postgis/__init__.py: no change ./django/contrib/gis/db/backends/postgis/adapter.py: no change ./django/contrib/gis/db/backends/postgis/base.py: no change ./django/contrib/gis/db/backends/postgis/const.py: no change ./django/contrib/gis/db/backends/postgis/features.py: no change ./django/contrib/gis/db/backends/postgis/introspection.py: no change ./django/contrib/gis/db/backends/postgis/models.py: no change ./django/contrib/gis/db/backends/postgis/operations.py: no change ./django/contrib/gis/db/backends/postgis/pgraster.py: no change recursedown('./django/contrib/contenttypes/locale/my') recursedown('./django/contrib/contenttypes/locale/my/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/nb') recursedown('./django/contrib/contenttypes/locale/nb/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ne') recursedown('./django/contrib/contenttypes/locale/ne/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/nl') recursedown('./django/contrib/contenttypes/locale/nl/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/nn') recursedown('./django/contrib/contenttypes/locale/nn/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/os') recursedown('./django/contrib/contenttypes/locale/os/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/pa') recursedown('./django/contrib/contenttypes/locale/pa/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/pl') recursedown('./django/contrib/contenttypes/locale/pl/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/pt') recursedown('./django/contrib/contenttypes/locale/pt/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/pt_BR') recursedown('./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ro') recursedown('./django/contrib/contenttypes/locale/ro/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ru') recursedown('./django/contrib/contenttypes/locale/ru/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sk') recursedown('./django/contrib/contenttypes/locale/sk/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sl') recursedown('./django/contrib/contenttypes/locale/sl/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sq') recursedown('./django/contrib/contenttypes/locale/sq/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sr') recursedown('./django/contrib/contenttypes/locale/sr/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sr_Latn') recursedown('./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sv') recursedown('./django/contrib/contenttypes/locale/sv/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/sw') recursedown('./django/contrib/contenttypes/locale/sw/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ta') recursedown('./django/contrib/contenttypes/locale/ta/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/te') recursedown('./django/contrib/contenttypes/locale/te/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/tg') recursedown('./django/contrib/contenttypes/locale/tg/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/th') recursedown('./django/contrib/contenttypes/locale/th/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/tk') recursedown('./django/contrib/contenttypes/locale/tk/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/tr') recursedown('./django/contrib/contenttypes/locale/tr/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/tt') recursedown('./django/contrib/contenttypes/locale/tt/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/udm') recursedown('./django/contrib/contenttypes/locale/udm/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ug') recursedown('./django/contrib/contenttypes/locale/ug/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/uk') recursedown('./django/contrib/contenttypes/locale/uk/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/ur') recursedown('./django/contrib/contenttypes/locale/ur/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/vi') recursedown('./django/contrib/contenttypes/locale/vi/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/zh_Hans') recursedown('./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/contenttypes/locale/zh_Hant') recursedown('./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/contenttypes/management') recursedown('./django/contrib/contenttypes/management/commands') recursedown('./django/contrib/contenttypes/migrations') recursedown('./django/contrib/flatpages') recursedown('./django/contrib/flatpages/locale') recursedown('./django/contrib/flatpages/locale/af') recursedown('./django/contrib/flatpages/locale/af/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ar') recursedown('./django/contrib/flatpages/locale/ar/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ar_DZ') recursedown('./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ast') recursedown('./django/contrib/flatpages/locale/ast/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/az') recursedown('./django/contrib/flatpages/locale/az/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/be') recursedown('./django/contrib/flatpages/locale/be/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/bg') recursedown('./django/contrib/flatpages/locale/bg/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/bn') recursedown('./django/contrib/flatpages/locale/bn/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/br') recursedown('./django/contrib/flatpages/locale/br/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/bs') recursedown('./django/contrib/flatpages/locale/bs/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ca') recursedown('./django/contrib/flatpages/locale/ca/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ckb') recursedown('./django/contrib/flatpages/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/cs') recursedown('./django/contrib/flatpages/locale/cs/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/cy') recursedown('./django/contrib/flatpages/locale/cy/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/da') recursedown('./django/contrib/flatpages/locale/da/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/de') recursedown('./django/contrib/flatpages/locale/de/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/dsb') recursedown('./django/contrib/flatpages/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/el') recursedown('./django/contrib/flatpages/locale/el/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/en') recursedown('./django/contrib/flatpages/locale/en/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/en_AU') recursedown('./django/contrib/flatpages/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/en_GB') recursedown('./django/contrib/flatpages/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/eo') recursedown('./django/contrib/flatpages/locale/eo/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/es') recursedown('./django/contrib/flatpages/locale/es/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/es_AR') recursedown('./django/contrib/flatpages/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/es_CO') recursedown('./django/contrib/flatpages/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/es_MX') recursedown('./django/contrib/flatpages/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/es_VE') recursedown('./django/contrib/flatpages/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/et') recursedown('./django/contrib/flatpages/locale/et/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/eu') recursedown('./django/contrib/flatpages/locale/eu/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/fa') recursedown('./django/contrib/flatpages/locale/fa/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/fi') recursedown('./django/contrib/flatpages/locale/fi/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/fr') recursedown('./django/contrib/flatpages/locale/fr/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/fy') recursedown('./django/contrib/flatpages/locale/fy/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ga') recursedown('./django/contrib/flatpages/locale/ga/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/gd') recursedown('./django/contrib/flatpages/locale/gd/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/gl') recursedown('./django/contrib/flatpages/locale/gl/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/he') recursedown('./django/contrib/flatpages/locale/he/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/hi') recursedown('./django/contrib/flatpages/locale/hi/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/hr') recursedown('./django/contrib/flatpages/locale/hr/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/hsb') recursedown('./django/contrib/flatpages/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/hu') recursedown('./django/contrib/flatpages/locale/hu/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/hy') recursedown('./django/contrib/flatpages/locale/hy/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ia') recursedown('./django/contrib/flatpages/locale/ia/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/id') recursedown('./django/contrib/flatpages/locale/id/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/io') recursedown('./django/contrib/flatpages/locale/io/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/is') recursedown('./django/contrib/flatpages/locale/is/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/it') recursedown('./django/contrib/flatpages/locale/it/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ja') recursedown('./django/contrib/flatpages/locale/ja/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ka') recursedown('./django/contrib/flatpages/locale/ka/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/kk') recursedown('./django/contrib/flatpages/locale/kk/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/km') recursedown('./django/contrib/flatpages/locale/km/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/kn') recursedown('./django/contrib/flatpages/locale/kn/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ko') recursedown('./django/contrib/flatpages/locale/ko/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ky') recursedown('./django/contrib/flatpages/locale/ky/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/lb') recursedown('./django/contrib/flatpages/locale/lb/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/lt') recursedown('./django/contrib/flatpages/locale/lt/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/lv') recursedown('./django/contrib/flatpages/locale/lv/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/mk') recursedown('./django/contrib/flatpages/locale/mk/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ml') recursedown('./django/contrib/flatpages/locale/ml/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/mn') recursedown('./django/contrib/flatpages/locale/mn/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/mr') recursedown('./django/contrib/flatpages/locale/mr/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ms') recursedown('./django/contrib/flatpages/locale/ms/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/my') recursedown('./django/contrib/flatpages/locale/my/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/nb') recursedown('./django/contrib/flatpages/locale/nb/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ne') recursedown('./django/contrib/flatpages/locale/ne/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/nl') recursedown('./django/contrib/flatpages/locale/nl/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/nn') recursedown('./django/contrib/flatpages/locale/nn/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/os') recursedown('./django/contrib/flatpages/locale/os/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/pa') recursedown('./django/contrib/flatpages/locale/pa/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/pl') recursedown('./django/contrib/flatpages/locale/pl/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/pt') recursedown('./django/contrib/flatpages/locale/pt/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/pt_BR') recursedown('./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ro') recursedown('./django/contrib/flatpages/locale/ro/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ru') recursedown('./django/contrib/flatpages/locale/ru/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sk') recursedown('./django/contrib/flatpages/locale/sk/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sl') recursedown('./django/contrib/flatpages/locale/sl/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sq') recursedown('./django/contrib/flatpages/locale/sq/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sr') recursedown('./django/contrib/flatpages/locale/sr/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sr_Latn') recursedown('./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sv') recursedown('./django/contrib/flatpages/locale/sv/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/sw') recursedown('./django/contrib/flatpages/locale/sw/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ta') recursedown('./django/contrib/flatpages/locale/ta/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/te') recursedown('./django/contrib/flatpages/locale/te/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/tg') recursedown('./django/contrib/flatpages/locale/tg/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/th') recursedown('./django/contrib/flatpages/locale/th/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/tk') recursedown('./django/contrib/flatpages/locale/tk/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/tr') recursedown('./django/contrib/flatpages/locale/tr/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/tt') recursedown('./django/contrib/flatpages/locale/tt/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/udm') recursedown('./django/contrib/flatpages/locale/udm/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ug') recursedown('./django/contrib/flatpages/locale/ug/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/uk') recursedown('./django/contrib/flatpages/locale/uk/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/ur') recursedown('./django/contrib/flatpages/locale/ur/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/vi') recursedown('./django/contrib/flatpages/locale/vi/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/zh_Hans') recursedown('./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/flatpages/locale/zh_Hant') recursedown('./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/flatpages/migrations') recursedown('./django/contrib/flatpages/templatetags') recursedown('./django/contrib/gis') recursedown('./django/contrib/gis/admin') recursedown('./django/contrib/gis/db') recursedown('./django/contrib/gis/db/backends') recursedown('./django/contrib/gis/db/backends/base') recursedown('./django/contrib/gis/db/backends/mysql') recursedown('./django/contrib/gis/db/backends/oracle') recursedown('./django/contrib/gis/db/backends/postgis') recursedown('./django/contrib/gis/db/backends/spatialite') recursedown('./django/contrib/gis/db/models') recursedown('./django/contrib/gis/db/models/sql') recursedown('./django/contrib/gis/forms') recursedown('./django/contrib/gis/gdal') recursedown('./django/contrib/gis/gdal/prototypes') recursedown('./django/contrib/gis/gdal/raster') recursedown('./django/contrib/gis/geoip2') recursedown('./django/contrib/gis/geos') recursedown('./django/contrib/gis/geos/prototypes') recursedown('./django/contrib/gis/locale') recursedown('./django/contrib/gis/locale/af') recursedown('./django/contrib/gis/locale/af/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ar') recursedown('./django/contrib/gis/locale/ar/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ar_DZ') recursedown('./django/contrib/gis/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ast') recursedown('./django/contrib/gis/locale/ast/LC_MESSAGES') recursedown('./django/contrib/gis/locale/az') recursedown('./django/contrib/gis/locale/az/LC_MESSAGES') recursedown('./django/contrib/gis/locale/be') recursedown('./django/contrib/gis/locale/be/LC_MESSAGES') recursedown('./django/contrib/gis/locale/bg') recursedown('./django/contrib/gis/locale/bg/LC_MESSAGES') recursedown('./django/contrib/gis/locale/bn') recursedown('./django/contrib/gis/locale/bn/LC_MESSAGES') recursedown('./django/contrib/gis/locale/br') recursedown('./django/contrib/gis/locale/br/LC_MESSAGES') recursedown('./django/contrib/gis/locale/bs') recursedown('./django/contrib/gis/locale/bs/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ca') recursedown('./django/contrib/gis/locale/ca/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ckb') recursedown('./django/contrib/gis/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/gis/locale/cs') recursedown('./django/contrib/gis/locale/cs/LC_MESSAGES') recursedown('./django/contrib/gis/locale/cy') recursedown('./django/contrib/gis/locale/cy/LC_MESSAGES') recursedown('./django/contrib/gis/locale/da') recursedown('./django/contrib/gis/locale/da/LC_MESSAGES') recursedown('./django/contrib/gis/locale/de') recursedown('./django/contrib/gis/locale/de/LC_MESSAGES') recursedown('./django/contrib/gis/locale/dsb') recursedown('./django/contrib/gis/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/gis/locale/el') recursedown('./django/contrib/gis/locale/el/LC_MESSAGES') recursedown('./django/contrib/gis/locale/en') recursedown('./django/contrib/gis/locale/en/LC_MESSAGES') recursedown('./django/contrib/gis/locale/en_AU') recursedown('./django/contrib/gis/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/gis/locale/en_GB') recursedown('./django/contrib/gis/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/gis/locale/eo') recursedown('./django/contrib/gis/locale/eo/LC_MESSAGES') recursedown('./django/contrib/gis/locale/es') recursedown('./django/contrib/gis/locale/es/LC_MESSAGES') recursedown('./django/contrib/gis/locale/es_AR') recursedown('./django/contrib/gis/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/gis/locale/es_CO') recursedown('./django/contrib/gis/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/gis/locale/es_MX') recursedown('./django/contrib/gis/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/gis/locale/es_VE') recursedown('./django/contrib/gis/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/gis/locale/et') recursedown('./django/contrib/gis/locale/et/LC_MESSAGES') recursedown('./django/contrib/gis/locale/eu') recursedown('./django/contrib/gis/locale/eu/LC_MESSAGES') recursedown('./django/contrib/gis/locale/fa') recursedown('./django/contrib/gis/locale/fa/LC_MESSAGES') recursedown('./django/contrib/gis/locale/fi') recursedown('./django/contrib/gis/locale/fi/LC_MESSAGES') recursedown('./django/contrib/gis/locale/fr') recursedown('./django/contrib/gis/locale/fr/LC_MESSAGES') recursedown('./django/contrib/gis/locale/fy') recursedown('./django/contrib/gis/locale/fy/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ga') recursedown('./django/contrib/gis/locale/ga/LC_MESSAGES') recursedown('./django/contrib/gis/locale/gd') recursedown('./django/contrib/gis/locale/gd/LC_MESSAGES') recursedown('./django/contrib/gis/locale/gl') recursedown('./django/contrib/gis/locale/gl/LC_MESSAGES') recursedown('./django/contrib/gis/locale/he') recursedown('./django/contrib/gis/locale/he/LC_MESSAGES') recursedown('./django/contrib/gis/locale/hi') recursedown('./django/contrib/gis/locale/hi/LC_MESSAGES') recursedown('./django/contrib/gis/locale/hr') recursedown('./django/contrib/gis/locale/hr/LC_MESSAGES') recursedown('./django/contrib/gis/locale/hsb') recursedown('./django/contrib/gis/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/gis/locale/hu') recursedown('./django/contrib/gis/locale/hu/LC_MESSAGES') recursedown('./django/contrib/gis/locale/hy') recursedown('./django/contrib/gis/locale/hy/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ia') recursedown('./django/contrib/gis/locale/ia/LC_MESSAGES') recursedown('./django/contrib/gis/locale/id') recursedown('./django/contrib/gis/locale/id/LC_MESSAGES') recursedown('./django/contrib/gis/locale/io') recursedown('./django/contrib/gis/locale/io/LC_MESSAGES') recursedown('./django/contrib/gis/locale/is') recursedown('./django/contrib/gis/locale/is/LC_MESSAGES') recursedown('./django/contrib/gis/locale/it') recursedown('./django/contrib/gis/locale/it/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ja') recursedown('./django/contrib/gis/locale/ja/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ka') recursedown('./django/contrib/gis/locale/ka/LC_MESSAGES') recursedown('./django/contrib/gis/locale/kk') recursedown('./django/contrib/gis/locale/kk/LC_MESSAGES') recursedown('./django/contrib/gis/locale/km') recursedown('./django/contrib/gis/locale/km/LC_MESSAGES') recursedown('./django/contrib/gis/locale/kn') recursedown('./django/contrib/gis/locale/kn/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ko') recursedown('./django/contrib/gis/locale/ko/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ky') recursedown('./django/contrib/gis/locale/ky/LC_MESSAGES') recursedown('./django/contrib/gis/locale/lb') recursedown('./django/contrib/gis/locale/lb/LC_MESSAGES') recursedown('./django/contrib/gis/locale/lt') recursedown('./django/contrib/gis/locale/lt/LC_MESSAGES') recursedown('./django/contrib/gis/locale/lv') recursedown('./django/contrib/gis/locale/lv/LC_MESSAGES') recursedown('./django/contrib/gis/locale/mk') recursedown('./django/contrib/gis/locale/mk/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ml') recursedown('./django/contrib/gis/locale/ml/LC_MESSAGES') recursedown('./django/contrib/gis/locale/mn') recursedown('./django/contrib/gis/locale/mn/LC_MESSAGES') recursedown('./django/contrib/gis/locale/mr') recursedown('./django/contrib/gis/locale/mr/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ms') recursedown('./django/contrib/gis/locale/ms/LC_MESSAGES') recursedown('./django/contrib/gis/locale/my') recursedown('./django/contrib/gis/locale/my/LC_MESSAGES') recursedown('./django/contrib/gis/locale/nb') recursedown('./django/contrib/gis/locale/nb/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ne') recursedown('./django/contrib/gis/locale/ne/LC_MESSAGES') recursedown('./django/contrib/gis/locale/nl') recursedown('./django/contrib/gis/locale/nl/LC_MESSAGES') recursedown('./django/contrib/gis/locale/nn') recursedown('./django/contrib/gis/locale/nn/LC_MESSAGES') recursedown('./django/contrib/gis/locale/os') recursedown('./django/contrib/gis/locale/os/LC_MESSAGES') recursedown('./django/contrib/gis/locale/pa') recursedown('./django/contrib/gis/locale/pa/LC_MESSAGES') recursedown('./django/contrib/gis/locale/pl') recursedown('./django/contrib/gis/locale/pl/LC_MESSAGES') recursedown('./django/contrib/gis/locale/pt') recursedown('./django/contrib/gis/locale/pt/LC_MESSAGES') recursedown('./django/contrib/gis/locale/pt_BR') recursedown('./django/contrib/gis/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ro') recursedown('./django/contrib/gis/locale/ro/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ru') recursedown('./django/contrib/gis/locale/ru/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sk') recursedown('./django/contrib/gis/locale/sk/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sl') recursedown('./django/contrib/gis/locale/sl/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sq') recursedown('./django/contrib/gis/locale/sq/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sr') recursedown('./django/contrib/gis/locale/sr/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sr_Latn') recursedown('./django/contrib/gis/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sv') recursedown('./django/contrib/gis/locale/sv/LC_MESSAGES') recursedown('./django/contrib/gis/locale/sw') recursedown('./django/contrib/gis/locale/sw/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ta') recursedown('./django/contrib/gis/locale/ta/LC_MESSAGES') recursedown('./django/contrib/gis/locale/te') recursedown('./django/contrib/gis/locale/te/LC_MESSAGES') recursedown('./django/contrib/gis/locale/tg') recursedown('./django/contrib/gis/locale/tg/LC_MESSAGES') recursedown('./django/contrib/gis/locale/th') recursedown('./django/contrib/gis/locale/th/LC_MESSAGES') recursedown('./django/contrib/gis/locale/tr') recursedown('./django/contrib/gis/locale/tr/LC_MESSAGES') recursedown('./django/contrib/gis/locale/tt') recursedown('./django/contrib/gis/locale/tt/LC_MESSAGES') recursedown('./django/contrib/gis/locale/udm') recursedown('./django/contrib/gis/locale/udm/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ug') recursedown('./django/contrib/gis/locale/ug/LC_MESSAGES') recursedown('./django/contrib/gis/locale/uk') recursedown('./django/contrib/gis/locale/uk/LC_MESSAGES') recursedown('./django/contrib/gis/locale/ur') recursedown('./django/contrib/gis/locale/ur/LC_MESSAGES') recursedown('./django/contrib/gis/locale/vi') recursedown('./django/contrib/gis/locale/vi/LC_MESSAGES') recursedown('./django/contrib/gis/locale/zh_Hans') recursedown('./django/contrib/gis/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/gis/locale/zh_Hant') recursedown('./django/contrib/gis/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/gis/management') recursedown('./django/contrib/gis/management/commands') recursedown('./django/contrib/gis/serializers') recursedown('./django/contrib/gis/sitemaps') recursedown('./django/contrib/gis/static') recursedown('./django/contrib/gis/static/gis') recursedown('./django/contrib/gis/static/gis/css') recursedown('./django/contrib/gis/static/gis/img') recursedown('./django/contrib/gis/static/gis/js') recursedown('./django/contrib/gis/templates') recursedown('./django/contrib/gis/templates/gis') recursedown('./django/contrib/gis/templates/gis/kml') recursedown('./django/contrib/gis/utils') recursedown('./django/contrib/humanize') recursedown('./django/contrib/humanize/locale') recursedown('./django/contrib/humanize/locale/af') recursedown('./django/contrib/humanize/locale/af/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ar') recursedown('./django/contrib/humanize/locale/ar/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ar_DZ') recursedown('./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ast') recursedown('./django/contrib/humanize/locale/ast/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/az') recursedown('./django/contrib/humanize/locale/az/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/be') recursedown('./django/contrib/humanize/locale/be/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/bg') recursedown('./django/contrib/humanize/locale/bg/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/bn') recursedown('./django/contrib/humanize/locale/bn/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/br') recursedown('./django/contrib/humanize/locale/br/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/bs') recursedown('./django/contrib/humanize/locale/bs/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ca') recursedown('./django/contrib/humanize/locale/ca/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ckb') recursedown('./django/contrib/humanize/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/cs') recursedown('./django/contrib/humanize/locale/cs/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/cy') recursedown('./django/contrib/humanize/locale/cy/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/da') recursedown('./django/contrib/humanize/locale/da/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/de') recursedown('./django/contrib/humanize/locale/de/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/dsb') recursedown('./django/contrib/humanize/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/el') recursedown('./django/contrib/humanize/locale/el/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/en') recursedown('./django/contrib/humanize/locale/en/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/en_AU') recursedown('./django/contrib/humanize/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/en_GB') recursedown('./django/contrib/humanize/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/eo') recursedown('./django/contrib/humanize/locale/eo/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/es') recursedown('./django/contrib/humanize/locale/es/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/es_AR') recursedown('./django/contrib/humanize/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/es_CO') recursedown('./django/contrib/humanize/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/es_MX') recursedown('./django/contrib/humanize/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/es_VE') recursedown('./django/contrib/humanize/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/et') recursedown('./django/contrib/humanize/locale/et/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/eu') recursedown('./django/contrib/humanize/locale/eu/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/fa') recursedown('./django/contrib/humanize/locale/fa/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/fi') recursedown('./django/contrib/humanize/locale/fi/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/fr') recursedown('./django/contrib/humanize/locale/fr/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/fy') recursedown('./django/contrib/humanize/locale/fy/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ga') recursedown('./django/contrib/humanize/locale/ga/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/gd') recursedown('./django/contrib/humanize/locale/gd/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/gl') recursedown('./django/contrib/humanize/locale/gl/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/he') recursedown('./django/contrib/humanize/locale/he/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/hi') recursedown('./django/contrib/humanize/locale/hi/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/hr') recursedown('./django/contrib/humanize/locale/hr/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/hsb') recursedown('./django/contrib/humanize/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/hu') recursedown('./django/contrib/humanize/locale/hu/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/hy') recursedown('./django/contrib/humanize/locale/hy/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ia') recursedown('./django/contrib/humanize/locale/ia/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/id') recursedown('./django/contrib/humanize/locale/id/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/io') recursedown('./django/contrib/humanize/locale/io/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/is') recursedown('./django/contrib/humanize/locale/is/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/it') recursedown('./django/contrib/humanize/locale/it/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ja') recursedown('./django/contrib/humanize/locale/ja/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ka') recursedown('./django/contrib/humanize/locale/ka/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/kk') recursedown('./django/contrib/humanize/locale/kk/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/km') recursedown('./django/contrib/humanize/locale/km/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/kn') recursedown('./django/contrib/humanize/locale/kn/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ko') recursedown('./django/contrib/humanize/locale/ko/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ky') recursedown('./django/contrib/humanize/locale/ky/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/lb') recursedown('./django/contrib/humanize/locale/lb/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/lt') recursedown('./django/contrib/humanize/locale/lt/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/lv') recursedown('./django/contrib/humanize/locale/lv/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/mk') recursedown('./django/contrib/humanize/locale/mk/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ml') recursedown('./django/contrib/humanize/locale/ml/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/mn') recursedown('./django/contrib/humanize/locale/mn/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/mr') recursedown('./django/contrib/humanize/locale/mr/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ms') recursedown('./django/contrib/humanize/locale/ms/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/my') recursedown('./django/contrib/humanize/locale/my/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/nb') recursedown('./django/contrib/humanize/locale/nb/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ne') recursedown('./django/contrib/humanize/locale/ne/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/nl') recursedown('./django/contrib/humanize/locale/nl/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/nn') recursedown('./django/contrib/humanize/locale/nn/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/os') recursedown('./django/contrib/humanize/locale/os/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/pa') recursedown('./django/contrib/humanize/locale/pa/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/pl') recursedown('./django/contrib/humanize/locale/pl/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/pt') recursedown('./django/contrib/humanize/locale/pt/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/pt_BR') recursedown('./django/contrib/humanize/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ro') recursedown('./django/contrib/humanize/locale/ro/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ru') recursedown('./django/contrib/humanize/locale/ru/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sk') recursedown('./django/contrib/humanize/locale/sk/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sl') recursedown('./django/contrib/humanize/locale/sl/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sq') recursedown('./django/contrib/humanize/locale/sq/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sr') recursedown('./django/contrib/humanize/locale/sr/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sr_Latn') recursedown('./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sv') recursedown('./django/contrib/humanize/locale/sv/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/sw') recursedown('./django/contrib/humanize/locale/sw/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ta') recursedown('./django/contrib/humanize/locale/ta/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/te') recursedown('./django/contrib/humanize/locale/te/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/tg') recursedown('./django/contrib/humanize/locale/tg/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/th') recursedown('./django/contrib/humanize/locale/th/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/tk') recursedown('./django/contrib/humanize/locale/tk/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/tr') recursedown('./django/contrib/humanize/locale/tr/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/tt') recursedown('./django/contrib/humanize/locale/tt/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/udm') recursedown('./django/contrib/humanize/locale/udm/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ug') recursedown('./django/contrib/humanize/locale/ug/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/uk') recursedown('./django/contrib/humanize/locale/uk/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/ur') recursedown('./django/contrib/humanize/locale/ur/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/uz') recursedown('./django/contrib/humanize/locale/uz/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/vi') recursedown('./django/contrib/humanize/locale/vi/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/zh_Hans') recursedown('./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/humanize/locale/zh_Hant') recursedown('./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/humanize/templatetags') recursedown('./django/contrib/messages') recursedown('./django/contrib/messages/storage') recursedown('./django/contrib/postgres') recursedown('./django/contrib/postgres/aggregates') recursedown('./django/contrib/postgres/fields') recursedown('./django/contrib/postgres/forms') recursedown('./django/contrib/postgres/jinja2') recursedown('./django/contrib/postgres/jinja2/postgres') recursedown('./django/contrib/postgres/jinja2/postgres/widgets') recursedown('./django/contrib/postgres/locale') recursedown('./django/contrib/postgres/locale/af') recursedown('./django/contrib/postgres/locale/af/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ar') recursedown('./django/contrib/postgres/locale/ar/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ar_DZ') recursedown('./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/az') recursedown('./django/contrib/postgres/locale/az/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/be') recursedown('./django/contrib/postgres/locale/be/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/bg') recursedown('./django/contrib/postgres/locale/bg/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ca') recursedown('./django/contrib/postgres/locale/ca/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ckb') recursedown('./django/contrib/postgres/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/cs') recursedown('./django/contrib/postgres/locale/cs/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/da') recursedown('./django/contrib/postgres/locale/da/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/de') recursedown('./django/contrib/postgres/locale/de/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/dsb') recursedown('./django/contrib/postgres/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/el') recursedown('./django/contrib/postgres/locale/el/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/en') recursedown('./django/contrib/postgres/locale/en/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/en_AU') recursedown('./django/contrib/postgres/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/eo') recursedown('./django/contrib/postgres/locale/eo/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/es') recursedown('./django/contrib/postgres/locale/es/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/es_AR') recursedown('./django/contrib/postgres/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/es_CO') recursedown('./django/contrib/postgres/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/es_MX') recursedown('./django/contrib/postgres/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/et') recursedown('./django/contrib/postgres/locale/et/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/eu') recursedown('./django/contrib/postgres/locale/eu/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/fa') recursedown('./django/contrib/postgres/locale/fa/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/fi') recursedown('./django/contrib/postgres/locale/fi/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/fr') recursedown('./django/contrib/postgres/locale/fr/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/gd') recursedown('./django/contrib/postgres/locale/gd/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/gl') recursedown('./django/contrib/postgres/locale/gl/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/he') recursedown('./django/contrib/postgres/locale/he/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/hr') recursedown('./django/contrib/postgres/locale/hr/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/hsb') recursedown('./django/contrib/postgres/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/hu') recursedown('./django/contrib/postgres/locale/hu/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/hy') recursedown('./django/contrib/postgres/locale/hy/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ia') recursedown('./django/contrib/postgres/locale/ia/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/id') recursedown('./django/contrib/postgres/locale/id/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/is') recursedown('./django/contrib/postgres/locale/is/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/it') recursedown('./django/contrib/postgres/locale/it/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ja') recursedown('./django/contrib/postgres/locale/ja/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ka') recursedown('./django/contrib/postgres/locale/ka/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/kk') recursedown('./django/contrib/postgres/locale/kk/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ko') recursedown('./django/contrib/postgres/locale/ko/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ky') recursedown('./django/contrib/postgres/locale/ky/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/lt') recursedown('./django/contrib/postgres/locale/lt/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/lv') recursedown('./django/contrib/postgres/locale/lv/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/mk') recursedown('./django/contrib/postgres/locale/mk/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ml') recursedown('./django/contrib/postgres/locale/ml/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/mn') recursedown('./django/contrib/postgres/locale/mn/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/mr') recursedown('./django/contrib/postgres/locale/mr/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ms') recursedown('./django/contrib/postgres/locale/ms/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/nb') recursedown('./django/contrib/postgres/locale/nb/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ne') recursedown('./django/contrib/postgres/locale/ne/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/nl') recursedown('./django/contrib/postgres/locale/nl/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/nn') recursedown('./django/contrib/postgres/locale/nn/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/pl') recursedown('./django/contrib/postgres/locale/pl/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/pt') recursedown('./django/contrib/postgres/locale/pt/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/pt_BR') recursedown('./django/contrib/postgres/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ro') recursedown('./django/contrib/postgres/locale/ro/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ru') recursedown('./django/contrib/postgres/locale/ru/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/sk') recursedown('./django/contrib/postgres/locale/sk/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/sl') recursedown('./django/contrib/postgres/locale/sl/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/sq') recursedown('./django/contrib/postgres/locale/sq/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/sr') recursedown('./django/contrib/postgres/locale/sr/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/sr_Latn') recursedown('./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/sv') recursedown('./django/contrib/postgres/locale/sv/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/tg') recursedown('./django/contrib/postgres/locale/tg/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/tk') recursedown('./django/contrib/postgres/locale/tk/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/tr') recursedown('./django/contrib/postgres/locale/tr/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/ug') recursedown('./django/contrib/postgres/locale/ug/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/uk') recursedown('./django/contrib/postgres/locale/uk/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/uz') recursedown('./django/contrib/postgres/locale/uz/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/zh_Hans') recursedown('./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/postgres/locale/zh_Hant') recursedown('./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/postgres/templates') recursedown('./django/contrib/postgres/templates/postgres') recursedown('./django/contrib/postgres/templates/postgres/widgets') recursedown('./django/contrib/redirects') recursedown('./django/contrib/redirects/locale') recursedown('./django/contrib/redirects/locale/af') recursedown('./django/contrib/redirects/locale/af/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ar') recursedown('./django/contrib/redirects/locale/ar/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ar_DZ') recursedown('./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ast') recursedown('./django/contrib/redirects/locale/ast/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/az') recursedown('./django/contrib/redirects/locale/az/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/be') recursedown('./django/contrib/redirects/locale/be/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/bg') recursedown('./django/contrib/redirects/locale/bg/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/bn') recursedown('./django/contrib/redirects/locale/bn/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/br') recursedown('./django/contrib/redirects/locale/br/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/bs') recursedown('./django/contrib/redirects/locale/bs/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ca') recursedown('./django/contrib/redirects/locale/ca/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ckb') recursedown('./django/contrib/redirects/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/cs') recursedown('./django/contrib/redirects/locale/cs/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/cy') recursedown('./django/contrib/redirects/locale/cy/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/da') recursedown('./django/contrib/redirects/locale/da/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/de') recursedown('./django/contrib/redirects/locale/de/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/dsb') recursedown('./django/contrib/redirects/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/el') recursedown('./django/contrib/redirects/locale/el/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/en') recursedown('./django/contrib/redirects/locale/en/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/en_AU') recursedown('./django/contrib/redirects/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/en_GB') recursedown('./django/contrib/redirects/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/eo') recursedown('./django/contrib/redirects/locale/eo/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/es') recursedown('./django/contrib/redirects/locale/es/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/es_AR') recursedown('./django/contrib/redirects/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/es_CO') recursedown('./django/contrib/redirects/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/es_MX') recursedown('./django/contrib/redirects/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/es_VE') recursedown('./django/contrib/redirects/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/et') recursedown('./django/contrib/redirects/locale/et/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/eu') recursedown('./django/contrib/redirects/locale/eu/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/fa') recursedown('./django/contrib/redirects/locale/fa/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/fi') recursedown('./django/contrib/redirects/locale/fi/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/fr') recursedown('./django/contrib/redirects/locale/fr/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/fy') recursedown('./django/contrib/redirects/locale/fy/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ga') recursedown('./django/contrib/redirects/locale/ga/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/gd') recursedown('./django/contrib/redirects/locale/gd/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/gl') recursedown('./django/contrib/redirects/locale/gl/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/he') recursedown('./django/contrib/redirects/locale/he/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/hi') recursedown('./django/contrib/redirects/locale/hi/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/hr') recursedown('./django/contrib/redirects/locale/hr/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/hsb') recursedown('./django/contrib/redirects/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/hu') recursedown('./django/contrib/redirects/locale/hu/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/hy') recursedown('./django/contrib/redirects/locale/hy/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ia') recursedown('./django/contrib/redirects/locale/ia/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/id') recursedown('./django/contrib/redirects/locale/id/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/io') recursedown('./django/contrib/redirects/locale/io/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/is') recursedown('./django/contrib/redirects/locale/is/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/it') recursedown('./django/contrib/redirects/locale/it/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ja') recursedown('./django/contrib/redirects/locale/ja/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ka') recursedown('./django/contrib/redirects/locale/ka/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/kab') recursedown('./django/contrib/redirects/locale/kab/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/kk') recursedown('./django/contrib/redirects/locale/kk/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/km') recursedown('./django/contrib/redirects/locale/km/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/kn') recursedown('./django/contrib/redirects/locale/kn/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ko') recursedown('./django/contrib/redirects/locale/ko/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ky') recursedown('./django/contrib/redirects/locale/ky/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/lb') recursedown('./django/contrib/redirects/locale/lb/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/lt') recursedown('./django/contrib/redirects/locale/lt/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/lv') recursedown('./django/contrib/redirects/locale/lv/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/mk') recursedown('./django/contrib/redirects/locale/mk/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ml') recursedown('./django/contrib/redirects/locale/ml/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/mn') recursedown('./django/contrib/redirects/locale/mn/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/mr') recursedown('./django/contrib/redirects/locale/mr/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ms') recursedown('./django/contrib/redirects/locale/ms/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/my') recursedown('./django/contrib/redirects/locale/my/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/nb') recursedown('./django/contrib/redirects/locale/nb/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ne') recursedown('./django/contrib/redirects/locale/ne/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/nl') recursedown('./django/contrib/redirects/locale/nl/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/nn') recursedown('./django/contrib/redirects/locale/nn/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/os') recursedown('./django/contrib/redirects/locale/os/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/pa') recursedown('./django/contrib/redirects/locale/pa/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/pl') recursedown('./django/contrib/redirects/locale/pl/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/pt') recursedown('./django/contrib/redirects/locale/pt/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/pt_BR') recursedown('./django/contrib/redirects/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ro') recursedown('./django/contrib/redirects/locale/ro/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ru') recursedown('./django/contrib/redirects/locale/ru/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sk') recursedown('./django/contrib/redirects/locale/sk/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sl') recursedown('./django/contrib/redirects/locale/sl/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sq') recursedown('./django/contrib/redirects/locale/sq/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sr') recursedown('./django/contrib/redirects/locale/sr/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sr_Latn') recursedown('./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sv') recursedown('./django/contrib/redirects/locale/sv/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/sw') recursedown('./django/contrib/redirects/locale/sw/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ta') recursedown('./django/contrib/redirects/locale/ta/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/te') recursedown('./django/contrib/redirects/locale/te/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/tg') recursedown('./django/contrib/redirects/locale/tg/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/th') recursedown('./django/contrib/redirects/locale/th/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/tk') recursedown('./django/contrib/redirects/locale/tk/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/tr') recursedown('./django/contrib/redirects/locale/tr/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/tt') recursedown('./django/contrib/redirects/locale/tt/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/udm') recursedown('./django/contrib/redirects/locale/udm/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ug') recursedown('./django/contrib/redirects/locale/ug/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/uk') recursedown('./django/contrib/redirects/locale/uk/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/ur') recursedown('./django/contrib/redirects/locale/ur/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/uz') recursedown('./django/contrib/redirects/locale/uz/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/vi') recursedown('./django/contrib/redirects/locale/vi/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/zh_Hans') recursedown('./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/redirects/locale/zh_Hant') recursedown('./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/redirects/migrations') recursedown('./django/contrib/sessions') recursedown('./django/contrib/sessions/backends') recursedown('./django/contrib/sessions/locale') recursedown('./django/contrib/sessions/locale/af') recursedown('./django/contrib/sessions/locale/af/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ar') recursedown('./django/contrib/sessions/locale/ar/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ar_DZ') recursedown('./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ast') recursedown('./django/contrib/sessions/locale/ast/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/az') recursedown('./django/contrib/sessions/locale/az/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/be') recursedown('./django/contrib/sessions/locale/be/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/bg') recursedown('./django/contrib/sessions/locale/bg/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/bn') recursedown('./django/contrib/sessions/locale/bn/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/br') recursedown('./django/contrib/sessions/locale/br/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/bs') recursedown('./django/contrib/sessions/locale/bs/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ca') recursedown('./django/contrib/sessions/locale/ca/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ckb') recursedown('./django/contrib/sessions/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/cs') recursedown('./django/contrib/sessions/locale/cs/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/cy') recursedown('./django/contrib/sessions/locale/cy/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/da') recursedown('./django/contrib/sessions/locale/da/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/de') recursedown('./django/contrib/sessions/locale/de/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/dsb') recursedown('./django/contrib/sessions/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/el') recursedown('./django/contrib/sessions/locale/el/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/en') recursedown('./django/contrib/sessions/locale/en/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/en_AU') recursedown('./django/contrib/sessions/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/en_GB') recursedown('./django/contrib/sessions/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/eo') recursedown('./django/contrib/sessions/locale/eo/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/es') recursedown('./django/contrib/sessions/locale/es/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/es_AR') recursedown('./django/contrib/sessions/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/es_CO') recursedown('./django/contrib/sessions/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/es_MX') recursedown('./django/contrib/sessions/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/es_VE') recursedown('./django/contrib/sessions/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/et') recursedown('./django/contrib/sessions/locale/et/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/eu') recursedown('./django/contrib/sessions/locale/eu/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/fa') recursedown('./django/contrib/sessions/locale/fa/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/fi') recursedown('./django/contrib/sessions/locale/fi/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/fr') recursedown('./django/contrib/sessions/locale/fr/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/fy') recursedown('./django/contrib/sessions/locale/fy/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ga') recursedown('./django/contrib/sessions/locale/ga/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/gd') recursedown('./django/contrib/sessions/locale/gd/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/gl') recursedown('./django/contrib/sessions/locale/gl/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/he') recursedown('./django/contrib/sessions/locale/he/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/hi') recursedown('./django/contrib/sessions/locale/hi/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/hr') recursedown('./django/contrib/sessions/locale/hr/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/hsb') recursedown('./django/contrib/sessions/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/hu') recursedown('./django/contrib/sessions/locale/hu/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/hy') recursedown('./django/contrib/sessions/locale/hy/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ia') recursedown('./django/contrib/sessions/locale/ia/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/id') recursedown('./django/contrib/sessions/locale/id/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/io') recursedown('./django/contrib/sessions/locale/io/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/is') recursedown('./django/contrib/sessions/locale/is/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/it') recursedown('./django/contrib/sessions/locale/it/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ja') recursedown('./django/contrib/sessions/locale/ja/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ka') recursedown('./django/contrib/sessions/locale/ka/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/kab') recursedown('./django/contrib/sessions/locale/kab/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/kk') recursedown('./django/contrib/sessions/locale/kk/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/km') recursedown('./django/contrib/sessions/locale/km/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/kn') recursedown('./django/contrib/sessions/locale/kn/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ko') recursedown('./django/contrib/sessions/locale/ko/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ky') recursedown('./django/contrib/sessions/locale/ky/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/lb') recursedown('./django/contrib/sessions/locale/lb/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/lt') recursedown('./django/contrib/sessions/locale/lt/LC_MESSAGES') ./django/contrib/gis/db/backends/postgis/schema.py: no change ./django/contrib/gis/db/backends/spatialite/__init__.py: no change ./django/contrib/gis/db/backends/spatialite/adapter.py: no change ./django/contrib/gis/db/backends/spatialite/base.py: no change ./django/contrib/gis/db/backends/spatialite/client.py: no change ./django/contrib/gis/db/backends/spatialite/features.py: no change ./django/contrib/gis/db/backends/spatialite/introspection.py: no change ./django/contrib/gis/db/backends/spatialite/models.py: no change ./django/contrib/gis/db/backends/spatialite/operations.py: no change ./django/contrib/gis/db/backends/spatialite/schema.py: no change ./django/contrib/gis/db/models/__init__.py: no change ./django/contrib/gis/db/models/aggregates.py: no change ./django/contrib/gis/db/models/fields.py: no change ./django/contrib/gis/db/models/functions.py: no change ./django/contrib/gis/db/models/lookups.py: no change ./django/contrib/gis/db/models/proxy.py: no change ./django/contrib/gis/db/models/sql/__init__.py: no change ./django/contrib/gis/db/models/sql/conversion.py: no change ./django/contrib/gis/forms/__init__.py: no change ./django/contrib/gis/forms/fields.py: no change ./django/contrib/gis/forms/widgets.py: no change ./django/contrib/gis/gdal/__init__.py: no change ./django/contrib/gis/gdal/base.py: no change ./django/contrib/gis/gdal/datasource.py: no change ./django/contrib/gis/gdal/driver.py: no change ./django/contrib/gis/gdal/envelope.py: no change ./django/contrib/gis/gdal/error.py: no change ./django/contrib/gis/gdal/feature.py: no change ./django/contrib/gis/gdal/field.py: no change ./django/contrib/gis/gdal/geometries.py: no change ./django/contrib/gis/gdal/geomtype.py: no change ./django/contrib/gis/gdal/layer.py: no change ./django/contrib/gis/gdal/libgdal.py: no change ./django/contrib/gis/gdal/srs.py: no change ./django/contrib/gis/gdal/prototypes/__init__.py: no change ./django/contrib/gis/gdal/prototypes/ds.py: no change ./django/contrib/gis/gdal/prototypes/errcheck.py: no change ./django/contrib/gis/gdal/prototypes/generation.py: no change ./django/contrib/gis/gdal/prototypes/geom.py: no change ./django/contrib/gis/gdal/prototypes/raster.py: no change ./django/contrib/gis/gdal/prototypes/srs.py: no change ./django/contrib/gis/gdal/raster/__init__.py: no change ./django/contrib/gis/gdal/raster/band.py: no change ./django/contrib/gis/gdal/raster/base.py: no change ./django/contrib/gis/gdal/raster/const.py: no change ./django/contrib/gis/gdal/raster/source.py: no change ./django/contrib/gis/geoip2/__init__.py: no change ./django/contrib/gis/geoip2/base.py: no change ./django/contrib/gis/geoip2/resources.py: no change ./django/contrib/gis/geos/__init__.py: no change ./django/contrib/gis/geos/base.py: no change ./django/contrib/gis/geos/collections.py: no change ./django/contrib/gis/geos/coordseq.py: no change ./django/contrib/gis/geos/error.py: no change ./django/contrib/gis/geos/factory.py: no change ./django/contrib/gis/geos/geometry.py: no change ./django/contrib/gis/geos/io.py: no change ./django/contrib/gis/geos/libgeos.py: no change ./django/contrib/gis/geos/linestring.py: no change ./django/contrib/gis/geos/mutable_list.py: no change ./django/contrib/gis/geos/point.py: no change ./django/contrib/gis/geos/polygon.py: no change ./django/contrib/gis/geos/prepared.py: no change ./django/contrib/gis/geos/prototypes/__init__.py: no change ./django/contrib/gis/geos/prototypes/coordseq.py: no change ./django/contrib/gis/geos/prototypes/errcheck.py: no change ./django/contrib/gis/geos/prototypes/geom.py: no change ./django/contrib/gis/geos/prototypes/io.py: no change ./django/contrib/gis/geos/prototypes/misc.py: no change ./django/contrib/gis/geos/prototypes/predicates.py: no change ./django/contrib/gis/geos/prototypes/prepared.py: no change ./django/contrib/gis/geos/prototypes/threadsafe.py: no change ./django/contrib/gis/geos/prototypes/topology.py: no change ./django/contrib/gis/management/__init__.py: no change ./django/contrib/gis/management/commands/__init__.py: no change ./django/contrib/gis/management/commands/inspectdb.py: no change ./django/contrib/gis/management/commands/ogrinspect.py: no change ./django/contrib/gis/serializers/__init__.py: no change ./django/contrib/gis/serializers/geojson.py: no change ./django/contrib/gis/sitemaps/__init__.py: no change ./django/contrib/gis/sitemaps/kml.py: no change ./django/contrib/gis/sitemaps/views.py: no change ./django/contrib/gis/utils/__init__.py: no change ./django/contrib/gis/utils/layermapping.py: no change ./django/contrib/gis/utils/ogrinfo.py: no change ./django/contrib/gis/utils/ogrinspect.py: no change ./django/contrib/gis/utils/srs.py: no change ./django/contrib/humanize/__init__.py: no change ./django/contrib/humanize/apps.py: no change ./django/contrib/humanize/templatetags/__init__.py: no change ./django/contrib/humanize/templatetags/humanize.py: no change ./django/contrib/messages/__init__.py: no change ./django/contrib/messages/api.py: no change ./django/contrib/messages/apps.py: no change ./django/contrib/messages/constants.py: no change ./django/contrib/messages/context_processors.py: no change ./django/contrib/messages/middleware.py: no change ./django/contrib/messages/test.py: no change ./django/contrib/messages/utils.py: no change ./django/contrib/messages/views.py: no change ./django/contrib/messages/storage/__init__.py: no change ./django/contrib/messages/storage/base.py: no change ./django/contrib/messages/storage/cookie.py: no change ./django/contrib/messages/storage/fallback.py: no change ./django/contrib/messages/storage/session.py: no change ./django/contrib/postgres/__init__.py: no change ./django/contrib/postgres/apps.py: no change ./django/contrib/postgres/constraints.py: no change ./django/contrib/postgres/expressions.py: no change ./django/contrib/postgres/functions.py: no change ./django/contrib/postgres/indexes.py: no change ./django/contrib/postgres/lookups.py: no change ./django/contrib/postgres/operations.py: no change ./django/contrib/postgres/search.py: no change ./django/contrib/postgres/serializers.py: no change ./django/contrib/postgres/signals.py: no change ./django/contrib/postgres/utils.py: no change ./django/contrib/postgres/validators.py: no change ./django/contrib/postgres/aggregates/__init__.py: no change ./django/contrib/postgres/aggregates/general.py: no change ./django/contrib/postgres/aggregates/mixins.py: no change ./django/contrib/postgres/aggregates/statistics.py: no change ./django/contrib/postgres/fields/__init__.py: no change ./django/contrib/postgres/fields/array.py: no change ./django/contrib/postgres/fields/citext.py: no change ./django/contrib/postgres/fields/hstore.py: no change ./django/contrib/postgres/fields/jsonb.py: no change ./django/contrib/postgres/fields/ranges.py: no change ./django/contrib/postgres/fields/utils.py: no change ./django/contrib/postgres/forms/__init__.py: no change ./django/contrib/postgres/forms/array.py: no change ./django/contrib/postgres/forms/hstore.py: no change ./django/contrib/postgres/forms/ranges.py: no change ./django/contrib/redirects/__init__.py: no change ./django/contrib/redirects/admin.py: no change ./django/contrib/redirects/apps.py: no change ./django/contrib/redirects/middleware.py: no change ./django/contrib/redirects/models.py: no change ./django/contrib/redirects/migrations/0001_initial.py: no change ./django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py: no change ./django/contrib/redirects/migrations/__init__.py: no change ./django/contrib/sessions/__init__.py: no change ./django/contrib/sessions/apps.py: no change ./django/contrib/sessions/base_session.py: no change ./django/contrib/sessions/exceptions.py: no change ./django/contrib/sessions/middleware.py: no change ./django/contrib/sessions/models.py: no change ./django/contrib/sessions/serializers.py: no change ./django/contrib/sessions/backends/__init__.py: no change ./django/contrib/sessions/backends/base.py: no change ./django/contrib/sessions/backends/cache.py: no change ./django/contrib/sessions/backends/cached_db.py: no change ./django/contrib/sessions/backends/db.py: no change ./django/contrib/sessions/backends/file.py: no change ./django/contrib/sessions/backends/signed_cookies.py: no change ./django/contrib/sessions/management/__init__.py: no change ./django/contrib/sessions/management/commands/__init__.py: no change ./django/contrib/sessions/management/commands/clearsessions.py: no change ./django/contrib/sessions/migrations/0001_initial.py: no change ./django/contrib/sessions/migrations/__init__.py: no change ./django/contrib/sitemaps/__init__.py: no change ./django/contrib/sitemaps/apps.py: no change ./django/contrib/sitemaps/views.py: no change ./django/contrib/sites/__init__.py: no change ./django/contrib/sites/admin.py: no change ./django/contrib/sites/apps.py: no change ./django/contrib/sites/checks.py: no change ./django/contrib/sites/management.py: no change ./django/contrib/sites/managers.py: no change ./django/contrib/sites/middleware.py: no change ./django/contrib/sites/models.py: no change ./django/contrib/sites/requests.py: no change ./django/contrib/sites/shortcuts.py: no change ./django/contrib/sites/migrations/0001_initial.py: no change ./django/contrib/sites/migrations/0002_alter_domain_unique.py: no change ./django/contrib/sites/migrations/__init__.py: no change ./django/contrib/staticfiles/__init__.py: no change ./django/contrib/staticfiles/apps.py: no change ./django/contrib/staticfiles/checks.py: no change ./django/contrib/staticfiles/finders.py: no change ./django/contrib/staticfiles/handlers.py: no change ./django/contrib/staticfiles/storage.py: no change ./django/contrib/staticfiles/testing.py: no change ./django/contrib/staticfiles/urls.py: no change ./django/contrib/staticfiles/utils.py: no change ./django/contrib/staticfiles/views.py: no change ./django/contrib/staticfiles/management/__init__.py: no change ./django/contrib/staticfiles/management/commands/__init__.py: no change ./django/contrib/staticfiles/management/commands/collectstatic.py: no change ./django/contrib/staticfiles/management/commands/findstatic.py: no change ./django/contrib/staticfiles/management/commands/runserver.py: no change ./django/contrib/syndication/__init__.py: no change ./django/contrib/syndication/apps.py: no change ./django/contrib/syndication/views.py: no change ./django/core/__init__.py: no change ./django/core/asgi.py: no change ./django/core/exceptions.py: no change ./django/core/paginator.py: no change ./django/core/signals.py: no change ./django/core/signing.py: no change ./django/core/validators.py: no change ./django/core/wsgi.py: no change ./django/core/cache/__init__.py: no change ./django/core/cache/utils.py: no change ./django/core/cache/backends/__init__.py: no change ./django/core/cache/backends/base.py: no change ./django/core/cache/backends/db.py: no change ./django/core/cache/backends/dummy.py: no change ./django/core/cache/backends/filebased.py: no change ./django/core/cache/backends/locmem.py: no change ./django/core/cache/backends/memcached.py: no change ./django/core/cache/backends/redis.py: no change ./django/core/checks/__init__.py: no change ./django/core/checks/async_checks.py: no change ./django/core/checks/caches.py: no change ./django/core/checks/database.py: no change ./django/core/checks/files.py: no change ./django/core/checks/messages.py: no change ./django/core/checks/model_checks.py: no change ./django/core/checks/registry.py: no change ./django/core/checks/templates.py: no change ./django/core/checks/translation.py: no change ./django/core/checks/urls.py: no change ./django/core/checks/compatibility/__init__.py: no change ./django/core/checks/compatibility/django_4_0.py: no change ./django/core/checks/security/__init__.py: no change ./django/core/checks/security/base.py: no change ./django/core/checks/security/csrf.py: no change ./django/core/checks/security/sessions.py: no change ./django/core/files/__init__.py: no change ./django/core/files/base.py: no change ./django/core/files/images.py: no change ./django/core/files/locks.py: no change ./django/core/files/move.py: no change ./django/core/files/temp.py: no change ./django/core/files/uploadedfile.py: no change ./django/core/files/uploadhandler.py: no change ./django/core/files/utils.py: no change ./django/core/files/storage/__init__.py: no change ./django/core/files/storage/base.py: no change ./django/core/files/storage/filesystem.py: no change ./django/core/files/storage/handler.py: no change ./django/core/files/storage/memory.py: no change ./django/core/files/storage/mixins.py: no change ./django/core/handlers/__init__.py: no change ./django/core/handlers/asgi.py: no change ./django/core/handlers/base.py: no change ./django/core/handlers/exception.py: no change ./django/core/handlers/wsgi.py: no change ./django/core/mail/__init__.py: no change ./django/core/mail/message.py: no change ./django/core/mail/utils.py: no change ./django/core/mail/backends/__init__.py: no change ./django/core/mail/backends/base.py: no change ./django/core/mail/backends/console.py: no change ./django/core/mail/backends/dummy.py: no change ./django/core/mail/backends/filebased.py: no change ./django/core/mail/backends/locmem.py: no change ./django/core/mail/backends/smtp.py: no change ./django/core/management/__init__.py: no change ./django/core/management/base.py: no change ./django/core/management/color.py: no change ./django/core/management/sql.py: no change ./django/core/management/templates.py: no change ./django/core/management/utils.py: no change ./django/core/management/commands/__init__.py: no change ./django/core/management/commands/check.py: no change ./django/core/management/commands/compilemessages.py: no change ./django/core/management/commands/createcachetable.py: no change ./django/core/management/commands/dbshell.py: no change ./django/core/management/commands/diffsettings.py: no change ./django/core/management/commands/dumpdata.py: no change ./django/core/management/commands/flush.py: no change ./django/core/management/commands/inspectdb.py: no change ./django/core/management/commands/loaddata.py: no change ./django/core/management/commands/makemessages.py: no change ./django/core/management/commands/makemigrations.py: no change ./django/core/management/commands/migrate.py: no change ./django/core/management/commands/optimizemigration.py: no change ./django/core/management/commands/runserver.py: no change ./django/core/management/commands/sendtestemail.py: no change ./django/core/management/commands/shell.py: no change ./django/core/management/commands/showmigrations.py: no change ./django/core/management/commands/sqlflush.py: no change ./django/core/management/commands/sqlmigrate.py: no change ./django/core/management/commands/sqlsequencereset.py: no change ./django/core/management/commands/squashmigrations.py: no change ./django/core/management/commands/startapp.py: no change ./django/core/management/commands/startproject.py: no change ./django/core/management/commands/test.py: no change ./django/core/management/commands/testserver.py: no change ./django/core/serializers/__init__.py: no change ./django/core/serializers/base.py: no change ./django/core/serializers/json.py: no change ./django/core/serializers/jsonl.py: no change ./django/core/serializers/python.py: no change ./django/core/serializers/pyyaml.py: no change ./django/core/serializers/xml_serializer.py: no change ./django/core/servers/__init__.py: no change ./django/core/servers/basehttp.py: no change ./django/db/__init__.py: no change ./django/db/transaction.py: no change ./django/db/utils.py: no change ./django/db/backends/__init__.py: no change ./django/db/backends/ddl_references.py: no change ./django/db/backends/signals.py: no change ./django/db/backends/utils.py: no change ./django/db/backends/base/__init__.py: no change ./django/db/backends/base/base.py: no change ./django/db/backends/base/client.py: no change ./django/db/backends/base/creation.py: no change ./django/db/backends/base/features.py: no change ./django/db/backends/base/introspection.py: no change ./django/db/backends/base/operations.py: no change ./django/db/backends/base/schema.py: no change ./django/db/backends/base/validation.py: no change ./django/db/backends/dummy/__init__.py: no change ./django/db/backends/dummy/base.py: no change ./django/db/backends/dummy/features.py: no change ./django/db/backends/mysql/__init__.py: no change ./django/db/backends/mysql/base.py: no change ./django/db/backends/mysql/client.py: no change ./django/db/backends/mysql/compiler.py: no change ./django/db/backends/mysql/creation.py: no change ./django/db/backends/mysql/features.py: no change ./django/db/backends/mysql/introspection.py: no change ./django/db/backends/mysql/operations.py: no change ./django/db/backends/mysql/schema.py: no change ./django/db/backends/mysql/validation.py: no change ./django/db/backends/oracle/__init__.py: no change ./django/db/backends/oracle/base.py: no change ./django/db/backends/oracle/client.py: no change ./django/db/backends/oracle/creation.py: no change ./django/db/backends/oracle/features.py: no change ./django/db/backends/oracle/functions.py: no change ./django/db/backends/oracle/introspection.py: no change ./django/db/backends/oracle/operations.py: no change ./django/db/backends/oracle/oracledb_any.py: no change ./django/db/backends/oracle/schema.py: no change ./django/db/backends/oracle/utils.py: no change ./django/db/backends/oracle/validation.py: no change ./django/db/backends/postgresql/__init__.py: no change ./django/db/backends/postgresql/base.py: no change ./django/db/backends/postgresql/client.py: no change ./django/db/backends/postgresql/creation.py: no change ./django/db/backends/postgresql/features.py: no change ./django/db/backends/postgresql/introspection.py: no change ./django/db/backends/postgresql/operations.py: no change ./django/db/backends/postgresql/psycopg_any.py: no change ./django/db/backends/postgresql/schema.py: no change ./django/db/backends/sqlite3/__init__.py: no change ./django/db/backends/sqlite3/_functions.py: no change ./django/db/backends/sqlite3/base.py: no change ./django/db/backends/sqlite3/client.py: no change ./django/db/backends/sqlite3/creation.py: no change ./django/db/backends/sqlite3/features.py: no change ./django/db/backends/sqlite3/introspection.py: no change ./django/db/backends/sqlite3/operations.py: no change ./django/db/backends/sqlite3/schema.py: no change ./django/db/migrations/__init__.py: no change ./django/db/migrations/autodetector.py: no change ./django/db/migrations/exceptions.py: no change ./django/db/migrations/executor.py: no change ./django/db/migrations/graph.py: no change ./django/db/migrations/loader.py: no change ./django/db/migrations/migration.py: no change ./django/db/migrations/optimizer.py: no change ./django/db/migrations/questioner.py: no change ./django/db/migrations/recorder.py: no change ./django/db/migrations/serializer.py: no change ./django/db/migrations/state.py: no change ./django/db/migrations/utils.py: no change ./django/db/migrations/writer.py: no change ./django/db/migrations/operations/__init__.py: no change ./django/db/migrations/operations/base.py: no change ./django/db/migrations/operations/fields.py: no change ./django/db/migrations/operations/models.py: no change ./django/db/migrations/operations/special.py: no change ./django/db/models/__init__.py: no change ./django/db/models/aggregates.py: no change ./django/db/models/base.py: no change ./django/db/models/constants.py: no change ./django/db/models/constraints.py: no change ./django/db/models/deletion.py: no change ./django/db/models/enums.py: no change ./django/db/models/expressions.py: no change ./django/db/models/indexes.py: no change ./django/db/models/lookups.py: no change ./django/db/models/manager.py: no change ./django/db/models/options.py: no change ./django/db/models/query.py: no change ./django/db/models/query_utils.py: no change ./django/db/models/signals.py: no change ./django/db/models/utils.py: no change ./django/db/models/fields/__init__.py: no change ./django/db/models/fields/files.py: no change ./django/db/models/fields/generated.py: no change ./django/db/models/fields/json.py: no change ./django/db/models/fields/mixins.py: no change ./django/db/models/fields/proxy.py: no change ./django/db/models/fields/related.py: no change ./django/db/models/fields/related_descriptors.py: no change ./django/db/models/fields/related_lookups.py: no change ./django/db/models/fields/reverse_related.py: no change ./django/db/models/functions/__init__.py: no change ./django/db/models/functions/comparison.py: no change ./django/db/models/functions/datetime.py: no change ./django/db/models/functions/math.py: no change ./django/db/models/functions/mixins.py: no change ./django/db/models/functions/text.py: no change ./django/db/models/functions/window.py: no change ./django/db/models/sql/__init__.py: no change ./django/db/models/sql/compiler.py: no change ./django/db/models/sql/constants.py: no change ./django/db/models/sql/datastructures.py: no change ./django/db/models/sql/query.py: no change ./django/db/models/sql/subqueries.py: no change ./django/db/models/sql/where.py: no change ./django/dispatch/__init__.py: no change ./django/dispatch/dispatcher.py: no change ./django/forms/__init__.py: no change ./django/forms/boundfield.py: no change ./django/forms/fields.py: no change ./django/forms/forms.py: no change ./django/forms/formsets.py: no change ./django/forms/models.py: no change ./django/forms/renderers.py: no change ./django/forms/utils.py: no change ./django/forms/widgets.py: no change ./django/http/__init__.py: no change ./django/http/cookie.py: no change ./django/http/multipartparser.py: no change ./django/http/request.py: no change ./django/http/response.py: no change ./django/middleware/__init__.py: no change ./django/middleware/cache.py: no change ./django/middleware/clickjacking.py: no change ./django/middleware/common.py: no change ./django/middleware/csrf.py: no change ./django/middleware/gzip.py: no change ./django/middleware/http.py: no change ./django/middleware/locale.py: no change ./django/middleware/security.py: no change ./django/template/__init__.py: no change ./django/template/autoreload.py: no change ./django/template/base.py: no change ./django/template/context.py: no change ./django/template/context_processors.py: no change ./django/template/defaultfilters.py: no change ./django/template/defaulttags.py: no change ./django/template/engine.py: no change ./django/template/exceptions.py: no change ./django/template/library.py: no change ./django/template/loader.py: no change ./django/template/loader_tags.py: no change ./django/template/response.py: no change ./django/template/smartif.py: no change ./django/template/utils.py: no change ./django/template/backends/__init__.py: no change ./django/template/backends/base.py: no change ./django/template/backends/django.py: no change ./django/template/backends/dummy.py: no change ./django/template/backends/jinja2.py: no change ./django/template/backends/utils.py: no change ./django/template/loaders/__init__.py: no change ./django/template/loaders/app_directories.py: no change ./django/template/loaders/base.py: no change ./django/template/loaders/cached.py: no change ./django/template/loaders/filesystem.py: no change ./django/template/loaders/locmem.py: no change ./django/templatetags/__init__.py: no change ./django/templatetags/cache.py: no change ./django/templatetags/i18n.py: no change ./django/templatetags/l10n.py: no change ./django/templatetags/static.py: no change ./django/templatetags/tz.py: no change ./django/test/__init__.py: no change ./django/test/client.py: no change ./django/test/html.py: no change ./django/test/runner.py: no change ./django/test/selenium.py: no change ./django/test/signals.py: no change ./django/test/testcases.py: no change ./django/test/utils.py: no change ./django/urls/__init__.py: no change ./django/urls/base.py: no change ./django/urls/conf.py: no change ./django/urls/converters.py: no change ./django/urls/exceptions.py: no change ./django/urls/resolvers.py: no change ./django/urls/utils.py: no change ./django/utils/__init__.py: no change ./django/utils/_os.py: no change ./django/utils/archive.py: no change ./django/utils/asyncio.py: no change ./django/utils/autoreload.py: no change ./django/utils/cache.py: no change ./django/utils/choices.py: no change ./django/utils/connection.py: no change ./django/utils/crypto.py: no change ./django/utils/datastructures.py: no change ./django/utils/dateformat.py: no change ./django/utils/dateparse.py: no change ./django/utils/dates.py: no change ./django/utils/deconstruct.py: no change ./django/utils/decorators.py: no change ./django/utils/deprecation.py: no change ./django/utils/duration.py: no change ./django/utils/encoding.py: no change ./django/utils/feedgenerator.py: no change ./django/utils/formats.py: no change ./django/utils/functional.py: no change ./django/utils/hashable.py: no change ./django/utils/html.py: no change ./django/utils/http.py: no change ./django/utils/inspect.py: no change ./django/utils/ipv6.py: no change ./django/utils/itercompat.py: no change ./django/utils/jslex.py: no change ./django/utils/log.py: no change ./django/utils/lorem_ipsum.py: no change ./django/utils/module_loading.py: no change ./django/utils/numberformat.py: no change ./django/utils/regex_helper.py: no change ./django/utils/safestring.py: no change ./django/utils/termcolors.py: no change ./django/utils/text.py: no change ./django/utils/timesince.py: no change ./django/utils/timezone.py: no change ./django/utils/tree.py: no change ./django/utils/version.py: no change ./django/utils/xmlutils.py: no change ./django/utils/translation/__init__.py: no change ./django/utils/translation/reloader.py: no change ./django/utils/translation/template.py: no change ./django/utils/translation/trans_null.py: no change ./django/utils/translation/trans_real.py: no change ./django/views/__init__.py: no change ./django/views/csrf.py: no change ./django/views/debug.py: no change ./django/views/defaults.py: no change ./django/views/i18n.py: no change ./django/views/static.py: no change ./django/views/decorators/__init__.py: no change ./django/views/decorators/cache.py: no change ./django/views/decorators/clickjacking.py: no change ./django/views/decorators/common.py: no change ./django/views/decorators/csrf.py: no change ./django/views/decorators/debug.py: no change ./django/views/decorators/gzip.py: no change ./django/views/decorators/http.py: no change ./django/views/decorators/vary.py: no change ./django/views/generic/__init__.py: no change ./django/views/generic/base.py: no change ./django/views/generic/dates.py: no change ./django/views/generic/detail.py: no change ./django/views/generic/edit.py: no change ./django/views/generic/list.py: no change ./docs/conf.py: no change ./docs/_ext/djangodocs.py: no change ./scripts/manage_translations.py: updating ./tests/runtests.py: updating ./tests/sitecustomize.py: no change ./tests/test_sqlite.py: no change ./tests/urls.py: no change ./tests/absolute_url_overrides/__init__.py: no change ./tests/absolute_url_overrides/tests.py: no change ./tests/admin_autodiscover/__init__.py: no change ./tests/admin_autodiscover/admin.py: no change ./tests/admin_autodiscover/models.py: no change ./tests/admin_autodiscover/tests.py: no change ./tests/admin_changelist/__init__.py: no change ./tests/admin_changelist/admin.py: no change ./tests/admin_changelist/models.py: no change ./tests/admin_changelist/test_date_hierarchy.py: no change ./tests/admin_changelist/tests.py: no change ./tests/admin_changelist/urls.py: no change ./tests/admin_checks/__init__.py: no change ./tests/admin_checks/models.py: no change ./tests/admin_checks/tests.py: no change ./tests/admin_custom_urls/__init__.py: no change ./tests/admin_custom_urls/models.py: no change ./tests/admin_custom_urls/tests.py: no change ./tests/admin_custom_urls/urls.py: no change ./tests/admin_default_site/__init__.py: no change ./tests/admin_default_site/apps.py: no change ./tests/admin_default_site/sites.py: no change ./tests/admin_default_site/tests.py: no change ./tests/admin_docs/__init__.py: no change ./tests/admin_docs/models.py: no change ./tests/admin_docs/namespace_urls.py: no change ./tests/admin_docs/test_middleware.py: no change ./tests/admin_docs/test_utils.py: no change ./tests/admin_docs/test_views.py: no change ./tests/admin_docs/tests.py: no change ./tests/admin_docs/urls.py: no change ./tests/admin_docs/views.py: no change ./tests/admin_filters/__init__.py: no change ./tests/admin_filters/models.py: no change ./tests/admin_filters/tests.py: no change ./tests/admin_inlines/__init__.py: no change ./tests/admin_inlines/admin.py: no change ./tests/admin_inlines/models.py: no change ./tests/admin_inlines/test_templates.py: no change ./tests/admin_inlines/tests.py: no change ./tests/admin_inlines/urls.py: no change ./tests/admin_ordering/__init__.py: no change ./tests/admin_ordering/models.py: no change ./tests/admin_ordering/tests.py: no change ./tests/admin_registration/__init__.py: no change ./tests/admin_registration/models.py: no change ./tests/admin_registration/tests.py: no change ./tests/admin_scripts/__init__.py: no change ./tests/admin_scripts/configured_dynamic_settings_manage.py: updating ./tests/admin_scripts/configured_settings_manage.py: updating ./tests/admin_scripts/tests.py: no change ./tests/admin_scripts/urls.py: no change ./tests/admin_scripts/another_app_waiting_migration/__init__.py: no change ./tests/admin_scripts/another_app_waiting_migration/models.py: no change ./tests/admin_scripts/another_app_waiting_migration/migrations/0001_initial.py: no change ./tests/admin_scripts/another_app_waiting_migration/migrations/__init__.py: no change ./tests/admin_scripts/app_raising_messages/__init__.py: no change ./tests/admin_scripts/app_raising_messages/models.py: no change ./tests/admin_scripts/app_raising_warning/__init__.py: no change ./tests/admin_scripts/app_raising_warning/models.py: no change ./tests/admin_scripts/app_waiting_migration/__init__.py: no change ./tests/admin_scripts/app_waiting_migration/models.py: no change ./tests/admin_scripts/app_waiting_migration/migrations/0001_initial.py: no change ./tests/admin_scripts/app_waiting_migration/migrations/__init__.py: no change ./tests/admin_scripts/app_with_import/__init__.py: no change ./tests/admin_scripts/app_with_import/models.py: no change ./tests/admin_scripts/broken_app/__init__.py: no change ./tests/admin_scripts/broken_app/models.py: no change ./tests/admin_scripts/complex_app/__init__.py: no change ./tests/admin_scripts/complex_app/admin/__init__.py: no change ./tests/admin_scripts/complex_app/admin/foo.py: no change ./tests/admin_scripts/complex_app/management/__init__.py: no change ./tests/admin_scripts/complex_app/management/commands/__init__.py: no change ./tests/admin_scripts/complex_app/management/commands/duplicate.py: no change ./tests/admin_scripts/complex_app/models/__init__.py: no change ./tests/admin_scripts/complex_app/models/bar.py: no change ./tests/admin_scripts/complex_app/models/foo.py: no change ./tests/admin_scripts/custom_templates/app_template/__init__.py: no change ./tests/admin_scripts/custom_templates/app_template/api.py: no change ./tests/admin_scripts/custom_templates/project_template/.hidden/render.py: no change ./tests/admin_scripts/custom_templates/project_template/additional_dir/additional_file.py: no change ./tests/admin_scripts/custom_templates/project_template/additional_dir/extra.py: no change ./tests/admin_scripts/custom_templates/project_template/additional_dir/localized.py: no change ./tests/admin_scripts/custom_templates/project_template/project_name/__init__.py: no change ./tests/admin_scripts/custom_templates/project_template/project_name/settings.py: no change ./tests/admin_scripts/management/__init__.py: no change ./tests/admin_scripts/management/commands/__init__.py: no change ./tests/admin_scripts/management/commands/app_command.py: no change ./tests/admin_scripts/management/commands/base_command.py: no change ./tests/admin_scripts/management/commands/custom_startproject.py: no change ./tests/admin_scripts/management/commands/label_command.py: no change ./tests/admin_scripts/management/commands/noargs_command.py: no change ./tests/admin_scripts/management/commands/suppress_base_options_command.py: no change ./tests/admin_scripts/simple_app/__init__.py: no change ./tests/admin_scripts/simple_app/models.py: no change ./tests/admin_scripts/simple_app/management/__init__.py: no change ./tests/admin_scripts/simple_app/management/commands/__init__.py: no change ./tests/admin_scripts/simple_app/management/commands/duplicate.py: no change ./tests/admin_utils/__init__.py: no change ./tests/admin_utils/admin.py: no change ./tests/admin_utils/models.py: no change ./tests/admin_utils/test_logentry.py: no change ./tests/admin_utils/tests.py: no change ./tests/admin_utils/urls.py: no change ./tests/admin_views/__init__.py: no change ./tests/admin_views/admin.py: no change ./tests/admin_views/custom_has_permission_admin.py: no change ./tests/admin_views/customadmin.py: no change ./tests/admin_views/forms.py: no change ./tests/admin_views/models.py: no change ./tests/admin_views/test_actions.py: no change ./tests/admin_views/test_adminsite.py: no change ./tests/admin_views/test_autocomplete_view.py: no change ./tests/admin_views/test_breadcrumbs.py: no change ./tests/admin_views/test_forms.py: no change ./tests/admin_views/test_history_view.py: no change ./tests/admin_views/test_multidb.py: no change ./tests/admin_views/test_nav_sidebar.py: no change ./tests/admin_views/test_related_object_lookups.py: no change ./tests/admin_views/test_skip_link_to_content.py: no change ./tests/admin_views/test_templatetags.py: no change ./tests/admin_views/tests.py: no change ./tests/admin_views/urls.py: no change ./tests/admin_views/views.py: no change ./tests/admin_widgets/__init__.py: no change ./tests/admin_widgets/models.py: no change ./tests/admin_widgets/test_autocomplete_widget.py: no change ./tests/admin_widgets/tests.py: no change ./tests/admin_widgets/urls.py: no change ./tests/admin_widgets/widgetadmin.py: no change ./tests/aggregation/__init__.py: no change ./tests/aggregation/models.py: no change ./tests/aggregation/test_filter_argument.py: no change ./tests/aggregation/tests.py: no change ./tests/aggregation_regress/__init__.py: no change ./tests/aggregation_regress/models.py: no change ./tests/aggregation_regress/tests.py: no change ./tests/annotations/__init__.py: no change ./tests/annotations/models.py: no change ./tests/annotations/tests.py: no change ./tests/app_loading/__init__.py: no change ./tests/app_loading/tests.py: no change ./tests/app_loading/not_installed/__init__.py: no change ./tests/app_loading/not_installed/models.py: no change ./tests/apps/__init__.py: no change ./tests/apps/apps.py: no change ./tests/apps/models.py: no change ./tests/apps/tests.py: no change ./tests/apps/namespace_package_base/nsapp/apps.py: no change ./tests/apps/no_config_app/__init__.py: no change ./tests/apps/one_config_app/__init__.py: no change ./tests/apps/one_config_app/apps.py: no change ./tests/apps/query_performing_app/__init__.py: no change ./tests/apps/query_performing_app/apps.py: no change ./tests/apps/two_configs_app/__init__.py: no change ./tests/apps/two_configs_app/apps.py: no change ./tests/apps/two_configs_one_default_app/__init__.py: no change ./tests/apps/two_configs_one_default_app/apps.py: no change ./tests/apps/two_default_configs_app/__init__.py: no change ./tests/apps/two_default_configs_app/apps.py: no change ./tests/asgi/__init__.py: no change ./tests/asgi/tests.py: no change ./tests/asgi/urls.py: no change ./tests/async/__init__.py: no change ./tests/async/models.py: no change ./tests/async/test_async_auth.py: no change ./tests/async/test_async_model_methods.py: no change ./tests/async/test_async_queryset.py: no change ./tests/async/test_async_related_managers.py: no change ./tests/async/test_async_shortcuts.py: no change ./tests/async/tests.py: no change ./tests/auth_tests/__init__.py: no change ./tests/auth_tests/backend_alias.py: no change ./tests/auth_tests/client.py: no change ./tests/auth_tests/settings.py: no change ./tests/auth_tests/test_admin_multidb.py: no change ./tests/auth_tests/test_auth_backends.py: no change ./tests/auth_tests/test_basic.py: no change ./tests/auth_tests/test_checks.py: no change ./tests/auth_tests/test_context_processors.py: no change ./tests/auth_tests/test_decorators.py: no change ./tests/auth_tests/test_forms.py: no change ./tests/auth_tests/test_handlers.py: no change ./tests/auth_tests/test_hashers.py: no change ./tests/auth_tests/test_management.py: no change ./tests/auth_tests/test_middleware.py: no change ./tests/auth_tests/test_migrations.py: no change ./tests/auth_tests/test_mixins.py: no change ./tests/auth_tests/test_models.py: no change ./tests/auth_tests/test_remote_user.py: no change ./tests/auth_tests/test_signals.py: no change ./tests/auth_tests/test_templates.py: no change ./tests/auth_tests/test_tokens.py: no change ./tests/auth_tests/test_validators.py: no change ./tests/auth_tests/test_views.py: no change ./tests/auth_tests/urls.py: no change ./tests/auth_tests/urls_admin.py: no change ./tests/auth_tests/urls_custom_user_admin.py: no change ./tests/auth_tests/models/__init__.py: no change ./tests/auth_tests/models/custom_permissions.py: no change ./tests/auth_tests/models/custom_user.py: no change ./tests/auth_tests/models/invalid_models.py: no change ./tests/auth_tests/models/is_active.py: no change ./tests/auth_tests/models/minimal.py: no change ./tests/auth_tests/models/no_password.py: no change ./tests/auth_tests/models/proxy.py: no change ./tests/auth_tests/models/uuid_pk.py: no change ./tests/auth_tests/models/with_custom_email_field.py: no change ./tests/auth_tests/models/with_foreign_key.py: no change ./tests/auth_tests/models/with_integer_username.py: no change ./tests/auth_tests/models/with_last_login_attr.py: no change ./tests/auth_tests/models/with_many_to_many.py: no change ./tests/auth_tests/models/with_unique_constraint.py: no change ./tests/backends/__init__.py: no change ./tests/backends/models.py: no change ./tests/backends/test_ddl_references.py: no change ./tests/backends/test_utils.py: no change ./tests/backends/tests.py: no change ./tests/backends/base/__init__.py: no change ./tests/backends/base/test_base.py: no change ./tests/backends/base/test_client.py: no change ./tests/backends/base/test_creation.py: no change ./tests/backends/base/test_features.py: no change ./tests/backends/base/test_introspection.py: no change ./tests/backends/base/test_operations.py: no change ./tests/backends/base/test_schema.py: no change ./tests/backends/base/app_unmigrated/__init__.py: no change ./tests/backends/base/app_unmigrated/models.py: no change ./tests/backends/base/app_unmigrated/migrations/0001_initial.py: no change ./tests/backends/base/app_unmigrated/migrations/__init__.py: no change ./tests/backends/mysql/__init__.py: no change ./tests/backends/mysql/test_creation.py: no change ./tests/backends/mysql/test_features.py: no change ./tests/backends/mysql/test_introspection.py: no change ./tests/backends/mysql/test_operations.py: no change ./tests/backends/mysql/test_schema.py: no change ./tests/backends/mysql/tests.py: no change ./tests/backends/oracle/__init__.py: no change ./tests/backends/oracle/test_creation.py: no change ./tests/backends/oracle/test_introspection.py: no change ./tests/backends/oracle/test_operations.py: no change ./tests/backends/oracle/tests.py: no change ./tests/backends/postgresql/__init__.py: no change ./tests/backends/postgresql/test_creation.py: no change ./tests/backends/postgresql/test_introspection.py: no change ./tests/backends/postgresql/test_operations.py: no change ./tests/backends/postgresql/test_server_side_cursors.py: no change ./tests/backends/postgresql/tests.py: no change ./tests/backends/sqlite/__init__.py: no change ./tests/backends/sqlite/test_creation.py: no change ./tests/backends/sqlite/test_features.py: no change ./tests/backends/sqlite/test_functions.py: no change ./tests/backends/sqlite/test_introspection.py: no change ./tests/backends/sqlite/test_operations.py: no change ./tests/backends/sqlite/tests.py: no change ./tests/base/__init__.py: no change ./tests/base/models.py: no change ./tests/bash_completion/__init__.py: no change ./tests/bash_completion/tests.py: no change ./tests/bash_completion/management/__init__.py: no change ./tests/bash_completion/management/commands/__init__.py: no change ./tests/bash_completion/management/commands/test_command.py: no change ./tests/basic/__init__.py: no change ./tests/basic/models.py: no change ./tests/basic/tests.py: no change ./tests/builtin_server/__init__.py: no change ./tests/builtin_server/tests.py: no change ./tests/builtin_server/urls.py: no change ./tests/builtin_server/views.py: no change ./tests/bulk_create/__init__.py: no change ./tests/bulk_create/models.py: no change ./tests/bulk_create/tests.py: no change ./tests/cache/__init__.py: no change ./tests/cache/closeable_cache.py: no change ./tests/cache/liberal_backend.py: no change ./tests/cache/models.py: no change ./tests/cache/tests.py: no change ./tests/cache/tests_async.py: no change ./tests/check_framework/__init__.py: no change ./tests/check_framework/apps.py: no change ./tests/check_framework/models.py: no change ./tests/check_framework/test_4_0_compatibility.py: no change ./tests/check_framework/test_async_checks.py: no change ./tests/check_framework/test_caches.py: no change ./tests/check_framework/test_database.py: no change ./tests/check_framework/test_files.py: no change ./tests/check_framework/test_model_checks.py: no change ./tests/check_framework/test_model_field_deprecation.py: no change ./tests/check_framework/test_multi_db.py: no change ./tests/check_framework/test_security.py: no change ./tests/check_framework/test_templates.py: no change ./tests/check_framework/test_translation.py: no change ./tests/check_framework/test_urls.py: no change ./tests/check_framework/tests.py: no change ./tests/check_framework/template_test_apps/__init__.py: no change ./tests/check_framework/template_test_apps/different_tags_app/__init__.py: no change ./tests/check_framework/template_test_apps/different_tags_app/apps.py: no change ./tests/check_framework/template_test_apps/different_tags_app/templatetags/__init__.py: no change ./tests/check_framework/template_test_apps/different_tags_app/templatetags/different_tags.py: no change ./tests/check_framework/template_test_apps/same_tags_app_1/__init__.py: no change ./tests/check_framework/template_test_apps/same_tags_app_1/apps.py: no change ./tests/check_framework/template_test_apps/same_tags_app_1/templatetags/__init__.py: no change ./tests/check_framework/template_test_apps/same_tags_app_1/templatetags/same_tags.py: no change ./tests/check_framework/template_test_apps/same_tags_app_2/__init__.py: no change ./tests/check_framework/template_test_apps/same_tags_app_2/apps.py: no change ./tests/check_framework/template_test_apps/same_tags_app_2/templatetags/__init__.py: no change ./tests/check_framework/template_test_apps/same_tags_app_2/templatetags/same_tags.py: no change ./tests/check_framework/urls/__init__.py: no change ./tests/check_framework/urls/bad_class_based_error_handlers.py: no change ./tests/check_framework/urls/bad_error_handlers_invalid_path.py: no change ./tests/check_framework/urls/bad_function_based_error_handlers.py: no change ./tests/check_framework/urls/beginning_with_slash.py: no change ./tests/check_framework/urls/cbv_as_view.py: no change ./tests/check_framework/urls/contains_tuple.py: no change ./tests/check_framework/urls/good_class_based_error_handlers.py: no change ./tests/check_framework/urls/good_function_based_error_handlers.py: no change ./tests/check_framework/urls/include_contains_tuple.py: no change ./tests/check_framework/urls/include_with_dollar.py: no change ./tests/check_framework/urls/name_with_colon.py: no change ./tests/check_framework/urls/no_warnings.py: no change ./tests/check_framework/urls/no_warnings_i18n.py: no change ./tests/check_framework/urls/non_unique_namespaces.py: no change ./tests/check_framework/urls/unique_namespaces.py: no change ./tests/check_framework/urls/warning_in_include.py: no change ./tests/check_framework/urls/path_compatibility/__init__.py: no change ./tests/check_framework/urls/path_compatibility/beginning_with_caret.py: no change ./tests/check_framework/urls/path_compatibility/contains_re_named_group.py: no change ./tests/check_framework/urls/path_compatibility/ending_with_dollar.py: no change ./tests/check_framework/urls/path_compatibility/matched_angle_brackets.py: no change ./tests/check_framework/urls/path_compatibility/unmatched_angle_brackets.py: no change ./tests/conditional_processing/__init__.py: no change ./tests/conditional_processing/tests.py: no change ./tests/conditional_processing/urls.py: no change ./tests/conditional_processing/views.py: no change ./tests/constraints/__init__.py: no change ./tests/constraints/models.py: no change ./tests/constraints/tests.py: no change ./tests/contenttypes_tests/__init__.py: no change ./tests/contenttypes_tests/models.py: no change ./tests/contenttypes_tests/test_checks.py: no change ./tests/contenttypes_tests/test_fields.py: no change ./tests/contenttypes_tests/test_management.py: no change ./tests/contenttypes_tests/test_migrations.py: no change ./tests/contenttypes_tests/test_models.py: no change ./tests/contenttypes_tests/test_operations.py: no change ./tests/contenttypes_tests/test_order_with_respect_to.py: no change ./tests/contenttypes_tests/test_views.py: no change ./tests/contenttypes_tests/urls.py: no change ./tests/contenttypes_tests/operations_migrations/0001_initial.py: no change ./tests/contenttypes_tests/operations_migrations/0002_rename_foo.py: no change ./tests/contenttypes_tests/operations_migrations/__init__.py: no change ./tests/context_processors/__init__.py: no change ./tests/context_processors/models.py: no change ./tests/context_processors/tests.py: no change ./tests/context_processors/urls.py: no change ./tests/context_processors/views.py: no change ./tests/csrf_tests/__init__.py: no change ./tests/csrf_tests/csrf_token_error_handler_urls.py: no change ./tests/csrf_tests/test_context_processor.py: no change ./tests/csrf_tests/tests.py: no change ./tests/csrf_tests/views.py: no change ./tests/custom_columns/__init__.py: no change ./tests/custom_columns/models.py: no change ./tests/custom_columns/tests.py: no change ./tests/custom_lookups/__init__.py: no change ./tests/custom_lookups/models.py: no change ./tests/custom_lookups/tests.py: no change ./tests/custom_managers/__init__.py: no change ./tests/custom_managers/models.py: no change ./tests/custom_managers/tests.py: no change ./tests/custom_methods/__init__.py: no change ./tests/custom_methods/models.py: no change ./tests/custom_methods/tests.py: no change ./tests/custom_migration_operations/__init__.py: no change ./tests/custom_migration_operations/more_operations.py: no change ./tests/custom_migration_operations/operations.py: no change ./tests/custom_pk/__init__.py: no change ./tests/custom_pk/fields.py: no change ./tests/custom_pk/models.py: no change ./tests/custom_pk/tests.py: no change ./tests/datatypes/__init__.py: no change ./tests/datatypes/models.py: no change ./tests/datatypes/tests.py: no change ./tests/dates/__init__.py: no change ./tests/dates/models.py: no change ./tests/dates/tests.py: no change ./tests/datetimes/__init__.py: no change ./tests/datetimes/models.py: no change ./tests/datetimes/tests.py: no change ./tests/db_functions/__init__.py: no change ./tests/db_functions/models.py: no change ./tests/db_functions/tests.py: no change ./tests/db_functions/comparison/__init__.py: no change ./tests/db_functions/comparison/test_cast.py: no change ./tests/db_functions/comparison/test_coalesce.py: no change ./tests/db_functions/comparison/test_collate.py: no change ./tests/db_functions/comparison/test_greatest.py: no change ./tests/db_functions/comparison/test_json_object.py: no change ./tests/db_functions/comparison/test_least.py: no change ./tests/db_functions/comparison/test_nullif.py: no change ./tests/db_functions/datetime/__init__.py: no change ./tests/db_functions/datetime/test_extract_trunc.py: no change ./tests/db_functions/datetime/test_now.py: no change ./tests/db_functions/math/__init__.py: no change ./tests/db_functions/math/test_abs.py: no change ./tests/db_functions/math/test_acos.py: no change ./tests/db_functions/math/test_asin.py: no change ./tests/db_functions/math/test_atan.py: no change ./tests/db_functions/math/test_atan2.py: no change ./tests/db_functions/math/test_ceil.py: no change ./tests/db_functions/math/test_cos.py: no change ./tests/db_functions/math/test_cot.py: no change ./tests/db_functions/math/test_degrees.py: no change ./tests/db_functions/math/test_exp.py: no change ./tests/db_functions/math/test_floor.py: no change ./tests/db_functions/math/test_ln.py: no change ./tests/db_functions/math/test_log.py: no change ./tests/db_functions/math/test_mod.py: no change ./tests/db_functions/math/test_pi.py: no change ./tests/db_functions/math/test_power.py: no change ./tests/db_functions/math/test_radians.py: no change ./tests/db_functions/math/test_random.py: no change ./tests/db_functions/math/test_round.py: no change ./tests/db_functions/math/test_sign.py: no change ./tests/db_functions/math/test_sin.py: no change ./tests/db_functions/math/test_sqrt.py: no change ./tests/db_functions/math/test_tan.py: no change ./tests/db_functions/migrations/0001_setup_extensions.py: no change ./tests/db_functions/migrations/0002_create_test_models.py: no change ./tests/db_functions/migrations/__init__.py: no change ./tests/db_functions/text/__init__.py: no change ./tests/db_functions/text/test_chr.py: no change ./tests/db_functions/text/test_concat.py: no change ./tests/db_functions/text/test_left.py: no change ./tests/db_functions/text/test_length.py: no change ./tests/db_functions/text/test_lower.py: no change ./tests/db_functions/text/test_md5.py: no change ./tests/db_functions/text/test_ord.py: no change ./tests/db_functions/text/test_pad.py: no change ./tests/db_functions/text/test_repeat.py: no change ./tests/db_functions/text/test_replace.py: no change ./tests/db_functions/text/test_reverse.py: no change ./tests/db_functions/text/test_right.py: no change ./tests/db_functions/text/test_sha1.py: no change ./tests/db_functions/text/test_sha224.py: no change ./tests/db_functions/text/test_sha256.py: no change ./tests/db_functions/text/test_sha384.py: no change ./tests/db_functions/text/test_sha512.py: no change ./tests/db_functions/text/test_strindex.py: no change ./tests/db_functions/text/test_substr.py: no change ./tests/db_functions/text/test_trim.py: no change ./tests/db_functions/text/test_upper.py: no change ./tests/db_functions/window/__init__.py: no change ./tests/db_functions/window/test_validation.py: no change ./tests/db_typecasts/__init__.py: no change ./tests/db_typecasts/tests.py: no change ./tests/db_utils/__init__.py: no change ./tests/db_utils/tests.py: no change ./tests/dbshell/__init__.py: no change ./tests/dbshell/fake_client.py: no change ./tests/dbshell/test_mysql.py: no change ./tests/dbshell/test_oracle.py: no change ./tests/dbshell/test_postgresql.py: no change ./tests/dbshell/test_sqlite.py: no change ./tests/dbshell/tests.py: no change ./tests/decorators/__init__.py: no change ./tests/decorators/test_cache.py: no change ./tests/decorators/test_clickjacking.py: no change ./tests/decorators/test_common.py: no change ./tests/decorators/test_csrf.py: no change ./tests/decorators/test_gzip.py: no change ./tests/decorators/test_http.py: no change ./tests/decorators/test_vary.py: no change ./tests/decorators/tests.py: no change ./tests/defer/__init__.py: no change ./tests/defer/models.py: no change ./tests/defer/tests.py: no change ./tests/defer_regress/__init__.py: no change ./tests/defer_regress/models.py: no change ./tests/defer_regress/tests.py: no change ./tests/delete/__init__.py: no change ./tests/delete/models.py: no change ./tests/delete/tests.py: no change ./tests/delete_regress/__init__.py: no change ./tests/delete_regress/models.py: no change ./tests/delete_regress/tests.py: no change ./tests/deprecation/__init__.py: no change ./tests/deprecation/test_middleware_mixin.py: no change ./tests/deprecation/test_storages.py: no change ./tests/deprecation/tests.py: no change ./tests/dispatch/__init__.py: no change ./tests/dispatch/tests.py: no change ./tests/distinct_on_fields/__init__.py: no change ./tests/distinct_on_fields/models.py: no change ./tests/distinct_on_fields/tests.py: no change ./tests/empty/__init__.py: no change ./tests/empty/models.py: no change ./tests/empty/tests.py: no change ./tests/empty/no_models/__init__.py: no change ./tests/empty_models/__init__.py: no change ./tests/empty_models/models.py: no change ./tests/empty_models/test_commands.py: no change ./tests/expressions/__init__.py: no change ./tests/expressions/models.py: no change ./tests/expressions/test_queryset_values.py: no change ./tests/expressions/tests.py: no change ./tests/expressions_case/__init__.py: no change ./tests/expressions_case/models.py: no change ./tests/expressions_case/tests.py: no change ./tests/expressions_window/__init__.py: no change ./tests/expressions_window/models.py: no change ./tests/expressions_window/tests.py: no change ./tests/extra_regress/__init__.py: no change ./tests/extra_regress/models.py: no change ./tests/extra_regress/tests.py: no change ./tests/field_deconstruction/__init__.py: no change ./tests/field_deconstruction/tests.py: no change ./tests/field_defaults/__init__.py: no change ./tests/field_defaults/models.py: no change ./tests/field_defaults/tests.py: no change ./tests/field_subclassing/__init__.py: no change ./tests/field_subclassing/fields.py: no change ./tests/field_subclassing/tests.py: no change ./tests/file_storage/__init__.py: no change ./tests/file_storage/models.py: no change ./tests/file_storage/test_base.py: no change ./tests/file_storage/test_generate_filename.py: no change ./tests/file_storage/test_inmemory_storage.py: no change ./tests/file_storage/tests.py: no change ./tests/file_storage/urls.py: no change ./tests/file_uploads/__init__.py: no change ./tests/file_uploads/models.py: no change ./tests/file_uploads/tests.py: no change ./tests/file_uploads/uploadhandler.py: no change ./tests/file_uploads/urls.py: no change ./tests/file_uploads/views.py: no change ./tests/files/__init__.py: no change ./tests/files/tests.py: no change ./tests/filtered_relation/__init__.py: no change ./tests/filtered_relation/models.py: no change ./tests/filtered_relation/tests.py: no change ./tests/fixtures/__init__.py: no change ./tests/fixtures/models.py: no change ./tests/fixtures/tests.py: no change ./tests/fixtures_model_package/__init__.py: no change ./tests/fixtures_model_package/tests.py: no change ./tests/fixtures_model_package/models/__init__.py: no change ./tests/fixtures_regress/__init__.py: no change ./tests/fixtures_regress/models.py: no change ./tests/fixtures_regress/tests.py: no change ./tests/flatpages_tests/__init__.py: no change ./tests/flatpages_tests/absolute_urls.py: no change ./tests/flatpages_tests/no_slash_urls.py: no change ./tests/flatpages_tests/settings.py: no change ./tests/flatpages_tests/test_csrf.py: no change ./tests/flatpages_tests/test_forms.py: no change ./tests/flatpages_tests/test_middleware.py: no change ./tests/flatpages_tests/test_models.py: no change ./tests/flatpages_tests/test_sitemaps.py: no change ./tests/flatpages_tests/test_templatetags.py: no change ./tests/flatpages_tests/test_views.py: no change ./tests/flatpages_tests/urls.py: no change ./tests/force_insert_update/__init__.py: no change ./tests/force_insert_update/models.py: no change ./tests/force_insert_update/tests.py: no change ./tests/foreign_object/__init__.py: no change ./tests/foreign_object/test_agnostic_order_trimjoin.py: no change ./tests/foreign_object/test_empty_join.py: no change ./tests/foreign_object/test_forms.py: no change ./tests/foreign_object/tests.py: no change ./tests/foreign_object/models/__init__.py: no change ./tests/foreign_object/models/article.py: no change ./tests/foreign_object/models/customers.py: no change ./tests/foreign_object/models/empty_join.py: no change ./tests/foreign_object/models/person.py: no change ./tests/forms_tests/__init__.py: no change ./tests/forms_tests/models.py: no change ./tests/forms_tests/urls.py: no change ./tests/forms_tests/views.py: no change ./tests/forms_tests/field_tests/__init__.py: no change ./tests/forms_tests/field_tests/test_base.py: no change ./tests/forms_tests/field_tests/test_booleanfield.py: no change ./tests/forms_tests/field_tests/test_charfield.py: no change ./tests/forms_tests/field_tests/test_choicefield.py: no change ./tests/forms_tests/field_tests/test_combofield.py: no change ./tests/forms_tests/field_tests/test_datefield.py: no change ./tests/forms_tests/field_tests/test_datetimefield.py: no change ./tests/forms_tests/field_tests/test_decimalfield.py: no change ./tests/forms_tests/field_tests/test_durationfield.py: no change ./tests/forms_tests/field_tests/test_emailfield.py: no change ./tests/forms_tests/field_tests/test_filefield.py: no change ./tests/forms_tests/field_tests/test_filepathfield.py: no change ./tests/forms_tests/field_tests/test_floatfield.py: no change ./tests/forms_tests/field_tests/test_genericipaddressfield.py: no change ./tests/forms_tests/field_tests/test_imagefield.py: no change ./tests/forms_tests/field_tests/test_integerfield.py: no change ./tests/forms_tests/field_tests/test_jsonfield.py: no change ./tests/forms_tests/field_tests/test_multiplechoicefield.py: no change ./tests/forms_tests/field_tests/test_multivaluefield.py: no change ./tests/forms_tests/field_tests/test_nullbooleanfield.py: no change ./tests/forms_tests/field_tests/test_regexfield.py: no change ./tests/forms_tests/field_tests/test_slugfield.py: no change ./tests/forms_tests/field_tests/test_splitdatetimefield.py: no change ./tests/forms_tests/field_tests/test_timefield.py: no change ./tests/forms_tests/field_tests/test_typedchoicefield.py: no change ./tests/forms_tests/field_tests/test_typedmultiplechoicefield.py: no change ./tests/forms_tests/field_tests/test_urlfield.py: no change ./tests/forms_tests/field_tests/test_uuidfield.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/__init__.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/a.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/ab.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/b.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/c/__init__.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/c/d.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/c/e.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/c/f/__init__.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/c/f/g.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/h/__init__.py: no change ./tests/forms_tests/field_tests/filepathfield_test_dir/j/__init__.py: no change ./tests/forms_tests/templatetags/__init__.py: no change ./tests/forms_tests/templatetags/tags.py: no change ./tests/forms_tests/tests/__init__.py: no change ./tests/forms_tests/tests/test_error_messages.py: no change ./tests/forms_tests/tests/test_forms.py: no change ./tests/forms_tests/tests/test_formsets.py: no change ./tests/forms_tests/tests/test_i18n.py: no change ./tests/forms_tests/tests/test_input_formats.py: no change ./tests/forms_tests/tests/test_media.py: no change ./tests/forms_tests/tests/test_renderers.py: no change ./tests/forms_tests/tests/test_utils.py: no change ./tests/forms_tests/tests/test_validators.py: no change ./tests/forms_tests/tests/test_widgets.py: no change ./tests/forms_tests/tests/tests.py: no change ./tests/forms_tests/widget_tests/__init__.py: no change ./tests/forms_tests/widget_tests/base.py: no change ./tests/forms_tests/widget_tests/test_checkboxinput.py: no change ./tests/forms_tests/widget_tests/test_checkboxselectmultiple.py: no change ./tests/forms_tests/widget_tests/test_choicewidget.py: no change ./tests/forms_tests/widget_tests/test_clearablefileinput.py: no change ./tests/forms_tests/widget_tests/test_dateinput.py: no change ./tests/forms_tests/widget_tests/test_datetimeinput.py: no change ./tests/forms_tests/widget_tests/test_fileinput.py: no change ./tests/forms_tests/widget_tests/test_hiddeninput.py: no change ./tests/forms_tests/widget_tests/test_input.py: no change ./tests/forms_tests/widget_tests/test_multiplehiddeninput.py: no change ./tests/forms_tests/widget_tests/test_multiwidget.py: no change ./tests/forms_tests/widget_tests/test_nullbooleanselect.py: no change ./tests/forms_tests/widget_tests/test_numberinput.py: no change ./tests/forms_tests/widget_tests/test_passwordinput.py: no change ./tests/forms_tests/widget_tests/test_radioselect.py: no change ./tests/forms_tests/widget_tests/test_select.py: no change ./tests/forms_tests/widget_tests/test_selectdatewidget.py: no change ./tests/forms_tests/widget_tests/test_selectmultiple.py: no change ./tests/forms_tests/widget_tests/test_splitdatetimewidget.py: no change ./tests/forms_tests/widget_tests/test_splithiddendatetimewidget.py: no change ./tests/forms_tests/widget_tests/test_textarea.py: no change ./tests/forms_tests/widget_tests/test_textinput.py: no change ./tests/forms_tests/widget_tests/test_timeinput.py: no change ./tests/forms_tests/widget_tests/test_widget.py: no change ./tests/from_db_value/__init__.py: no change ./tests/from_db_value/models.py: no change ./tests/from_db_value/tests.py: no change ./tests/generic_inline_admin/__init__.py: no change ./tests/generic_inline_admin/admin.py: no change ./tests/generic_inline_admin/models.py: no change ./tests/generic_inline_admin/tests.py: no change ./tests/generic_inline_admin/urls.py: no change ./tests/generic_relations/__init__.py: no change ./tests/generic_relations/models.py: no change ./tests/generic_relations/test_forms.py: no change ./tests/generic_relations/tests.py: no change ./tests/generic_relations_regress/__init__.py: no change ./tests/generic_relations_regress/models.py: no change ./tests/generic_relations_regress/tests.py: no change ./tests/generic_views/__init__.py: no change ./tests/generic_views/forms.py: no change ./tests/generic_views/models.py: no change ./tests/generic_views/test_base.py: no change ./tests/generic_views/test_dates.py: no change ./tests/generic_views/test_detail.py: no change ./tests/generic_views/test_edit.py: no change ./tests/generic_views/test_list.py: no change ./tests/generic_views/urls.py: no change ./tests/generic_views/views.py: no change ./tests/get_earliest_or_latest/__init__.py: no change ./tests/get_earliest_or_latest/models.py: no change ./tests/get_earliest_or_latest/tests.py: no change ./tests/get_object_or_404/__init__.py: no change ./tests/get_object_or_404/models.py: no change ./tests/get_object_or_404/tests.py: no change ./tests/get_or_create/__init__.py: no change ./tests/get_or_create/models.py: no change ./tests/get_or_create/tests.py: no change ./tests/gis_tests/__init__.py: no change ./tests/gis_tests/admin.py: no change ./tests/gis_tests/models.py: no change ./tests/gis_tests/test_data.py: no change ./tests/gis_tests/test_fields.py: no change ./tests/gis_tests/test_geoforms.py: no change ./tests/gis_tests/test_geoip2.py: no change ./tests/gis_tests/test_gis_tests_utils.py: no change ./tests/gis_tests/test_measure.py: no change ./tests/gis_tests/test_ptr.py: no change ./tests/gis_tests/test_spatialrefsys.py: no change ./tests/gis_tests/tests.py: no change ./tests/gis_tests/utils.py: no change ./tests/gis_tests/data/__init__.py: no change ./tests/gis_tests/data/rasters/__init__.py: no change ./tests/gis_tests/data/rasters/textrasters.py: no change ./tests/gis_tests/distapp/__init__.py: no change ./tests/gis_tests/distapp/models.py: no change ./tests/gis_tests/distapp/tests.py: no change ./tests/gis_tests/gdal_tests/__init__.py: no change ./tests/gis_tests/gdal_tests/test_driver.py: no change ./tests/gis_tests/gdal_tests/test_ds.py: no change ./tests/gis_tests/gdal_tests/test_envelope.py: no change ./tests/gis_tests/gdal_tests/test_geom.py: no change ./tests/gis_tests/gdal_tests/test_raster.py: no change ./tests/gis_tests/gdal_tests/test_srs.py: no change ./tests/gis_tests/gdal_tests/tests.py: no change ./tests/gis_tests/geo3d/__init__.py: no change ./tests/gis_tests/geo3d/models.py: no change ./tests/gis_tests/geo3d/tests.py: no change ./tests/gis_tests/geo3d/views.py: no change ./tests/gis_tests/geoadmin/__init__.py: no change ./tests/gis_tests/geoadmin/models.py: no change ./tests/gis_tests/geoadmin/tests.py: no change ./tests/gis_tests/geoadmin/urls.py: no change ./tests/gis_tests/geoapp/__init__.py: no change ./tests/gis_tests/geoapp/feeds.py: no change ./tests/gis_tests/geoapp/models.py: no change ./tests/gis_tests/geoapp/sitemaps.py: no change ./tests/gis_tests/geoapp/test_expressions.py: no change ./tests/gis_tests/geoapp/test_feeds.py: no change ./tests/gis_tests/geoapp/test_functions.py: no change ./tests/gis_tests/geoapp/test_indexes.py: no change ./tests/gis_tests/geoapp/test_regress.py: no change ./tests/gis_tests/geoapp/test_serializers.py: no change ./tests/gis_tests/geoapp/test_sitemaps.py: no change ./tests/gis_tests/geoapp/tests.py: no change ./tests/gis_tests/geoapp/urls.py: no change ./tests/gis_tests/geogapp/__init__.py: no change ./tests/gis_tests/geogapp/models.py: no change ./tests/gis_tests/geogapp/tests.py: no change ./tests/gis_tests/geos_tests/__init__.py: no change ./tests/gis_tests/geos_tests/test_coordseq.py: no change ./tests/gis_tests/geos_tests/test_geos.py: no change ./tests/gis_tests/geos_tests/test_geos_mutation.py: no change ./tests/gis_tests/geos_tests/test_io.py: no change ./tests/gis_tests/geos_tests/test_mutable_list.py: no change ./tests/gis_tests/gis_migrations/__init__.py: no change ./tests/gis_tests/gis_migrations/test_commands.py: no change ./tests/gis_tests/gis_migrations/test_operations.py: no change ./tests/gis_tests/gis_migrations/migrations/0001_setup_extensions.py: no change ./tests/gis_tests/gis_migrations/migrations/0002_create_models.py: no change ./tests/gis_tests/gis_migrations/migrations/__init__.py: no change ./tests/gis_tests/inspectapp/__init__.py: no change ./tests/gis_tests/inspectapp/models.py: no change ./tests/gis_tests/inspectapp/tests.py: no change ./tests/gis_tests/layermap/__init__.py: no change ./tests/gis_tests/layermap/models.py: no change ./tests/gis_tests/layermap/tests.py: no change ./tests/gis_tests/rasterapp/__init__.py: no change ./tests/gis_tests/rasterapp/models.py: no change ./tests/gis_tests/rasterapp/test_rasterfield.py: no change ./tests/gis_tests/rasterapp/migrations/0001_setup_extensions.py: no change ./tests/gis_tests/rasterapp/migrations/0002_rastermodels.py: no change ./tests/gis_tests/rasterapp/migrations/__init__.py: no change ./tests/gis_tests/relatedapp/__init__.py: no change ./tests/gis_tests/relatedapp/models.py: no change ./tests/gis_tests/relatedapp/tests.py: no change ./tests/handlers/__init__.py: no change ./tests/handlers/test_exception.py: no change ./tests/handlers/tests.py: no change ./tests/handlers/tests_custom_error_handlers.py: no change ./tests/handlers/urls.py: no change ./tests/handlers/views.py: no change ./tests/httpwrappers/__init__.py: no change ./tests/httpwrappers/tests.py: no change ./tests/humanize_tests/__init__.py: no change ./tests/humanize_tests/tests.py: no change ./tests/i18n/__init__.py: no change ./tests/i18n/forms.py: no change ./tests/i18n/models.py: no change ./tests/i18n/test_compilation.py: no change ./tests/i18n/test_extraction.py: no change ./tests/i18n/test_management.py: no change ./tests/i18n/test_percents.py: no change ./tests/i18n/tests.py: no change ./tests/i18n/urls.py: no change ./tests/i18n/urls_default_unprefixed.py: no change ./tests/i18n/utils.py: no change ./tests/i18n/commands/__init__.py: no change ./tests/i18n/contenttypes/__init__.py: no change ./tests/i18n/contenttypes/tests.py: no change ./tests/i18n/exclude/__init__.py: no change ./tests/i18n/loading_app/__init__.py: no change ./tests/i18n/loading_app/apps.py: no change ./tests/i18n/obsolete_translations/__init__.py: no change ./tests/i18n/other/__init__.py: no change ./tests/i18n/other/locale/__init__.py: no change ./tests/i18n/other/locale/de/__init__.py: no change ./tests/i18n/other/locale/de/formats.py: no change ./tests/i18n/other/locale/fr/__init__.py: no change ./tests/i18n/other/locale/fr/formats.py: no change ./tests/i18n/other2/__init__.py: no change ./tests/i18n/other2/locale/__init__.py: no change ./tests/i18n/other2/locale/de/__init__.py: no change ./tests/i18n/other2/locale/de/formats.py: no change ./tests/i18n/patterns/__init__.py: no change ./tests/i18n/patterns/tests.py: no change ./tests/i18n/patterns/urls/__init__.py: no change ./tests/i18n/patterns/urls/default.py: no change ./tests/i18n/patterns/urls/disabled.py: no change ./tests/i18n/patterns/urls/included.py: no change ./tests/i18n/patterns/urls/namespace.py: no change ./tests/i18n/patterns/urls/path_unused.py: no change ./tests/i18n/patterns/urls/wrong.py: no change ./tests/i18n/patterns/urls/wrong_namespace.py: no change ./tests/i18n/project_dir/__init__.py: no change ./tests/i18n/project_dir/app_no_locale/__init__.py: no change ./tests/i18n/project_dir/app_no_locale/models.py: no change ./tests/i18n/project_dir/app_with_locale/__init__.py: no change ./tests/i18n/project_dir/app_with_locale/models.py: no change ./tests/i18n/resolution/__init__.py: no change ./tests/i18n/sampleproject/manage.py: updating ./tests/i18n/sampleproject/update_catalogs.py: updating ./tests/i18n/sampleproject/sampleproject/__init__.py: no change ./tests/i18n/sampleproject/sampleproject/settings.py: no change ./tests/i18n/territorial_fallback/__init__.py: no change ./tests/i18n/unchanged/__init__.py: no change ./tests/import_error_package/__init__.py: no change ./tests/indexes/__init__.py: no change ./tests/indexes/models.py: no change ./tests/indexes/tests.py: no change ./tests/inline_formsets/__init__.py: no change ./tests/inline_formsets/models.py: no change ./tests/inline_formsets/tests.py: no change ./tests/inspectdb/__init__.py: no change ./tests/inspectdb/models.py: no change ./tests/inspectdb/tests.py: no change ./tests/introspection/__init__.py: no change ./tests/introspection/models.py: no change ./tests/introspection/tests.py: no change ./tests/invalid_models_tests/__init__.py: no change ./tests/invalid_models_tests/test_backend_specific.py: no change ./tests/invalid_models_tests/test_custom_fields.py: no change ./tests/invalid_models_tests/test_deprecated_fields.py: no change ./tests/invalid_models_tests/test_models.py: no change ./tests/invalid_models_tests/test_ordinary_fields.py: no change ./tests/invalid_models_tests/test_relative_fields.py: no change ./tests/known_related_objects/__init__.py: no change ./tests/known_related_objects/models.py: no change ./tests/known_related_objects/tests.py: no change ./tests/logging_tests/__init__.py: no change ./tests/logging_tests/logconfig.py: no change ./tests/logging_tests/tests.py: no change ./tests/logging_tests/urls.py: no change ./tests/logging_tests/urls_i18n.py: no change ./tests/logging_tests/views.py: no change ./tests/lookup/__init__.py: no change ./tests/lookup/models.py: no change ./tests/lookup/test_decimalfield.py: no change ./tests/lookup/test_lookups.py: no change ./tests/lookup/test_timefield.py: no change ./tests/lookup/tests.py: no change ./tests/m2m_and_m2o/__init__.py: no change ./tests/m2m_and_m2o/models.py: no change ./tests/m2m_and_m2o/tests.py: no change ./tests/m2m_intermediary/__init__.py: no change ./tests/m2m_intermediary/models.py: no change ./tests/m2m_intermediary/tests.py: no change ./tests/m2m_multiple/__init__.py: no change ./tests/m2m_multiple/models.py: no change ./tests/m2m_multiple/tests.py: no change ./tests/m2m_recursive/__init__.py: no change ./tests/m2m_recursive/models.py: no change ./tests/m2m_recursive/tests.py: no change ./tests/m2m_regress/__init__.py: no change ./tests/m2m_regress/models.py: no change ./tests/m2m_regress/tests.py: no change ./tests/m2m_signals/__init__.py: no change ./tests/m2m_signals/models.py: no change ./tests/m2m_signals/tests.py: no change ./tests/m2m_through/__init__.py: no change ./tests/m2m_through/models.py: no change ./tests/m2m_through/tests.py: no change ./tests/m2m_through_regress/__init__.py: no change ./tests/m2m_through_regress/models.py: no change ./tests/m2m_through_regress/test_multitable.py: no change ./tests/m2m_through_regress/tests.py: no change ./tests/m2o_recursive/__init__.py: no change ./tests/m2o_recursive/models.py: no change recursedown('./django/contrib/sessions/locale/lv') recursedown('./django/contrib/sessions/locale/lv/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/mk') recursedown('./django/contrib/sessions/locale/mk/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ml') recursedown('./django/contrib/sessions/locale/ml/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/mn') recursedown('./django/contrib/sessions/locale/mn/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/mr') recursedown('./django/contrib/sessions/locale/mr/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ms') recursedown('./django/contrib/sessions/locale/ms/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/my') recursedown('./django/contrib/sessions/locale/my/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/nb') recursedown('./django/contrib/sessions/locale/nb/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ne') recursedown('./django/contrib/sessions/locale/ne/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/nl') recursedown('./django/contrib/sessions/locale/nl/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/nn') recursedown('./django/contrib/sessions/locale/nn/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/os') recursedown('./django/contrib/sessions/locale/os/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/pa') recursedown('./django/contrib/sessions/locale/pa/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/pl') recursedown('./django/contrib/sessions/locale/pl/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/pt') recursedown('./django/contrib/sessions/locale/pt/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/pt_BR') recursedown('./django/contrib/sessions/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ro') recursedown('./django/contrib/sessions/locale/ro/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ru') recursedown('./django/contrib/sessions/locale/ru/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sk') recursedown('./django/contrib/sessions/locale/sk/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sl') recursedown('./django/contrib/sessions/locale/sl/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sq') recursedown('./django/contrib/sessions/locale/sq/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sr') recursedown('./django/contrib/sessions/locale/sr/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sr_Latn') recursedown('./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sv') recursedown('./django/contrib/sessions/locale/sv/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/sw') recursedown('./django/contrib/sessions/locale/sw/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ta') recursedown('./django/contrib/sessions/locale/ta/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/te') recursedown('./django/contrib/sessions/locale/te/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/tg') recursedown('./django/contrib/sessions/locale/tg/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/th') recursedown('./django/contrib/sessions/locale/th/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/tk') recursedown('./django/contrib/sessions/locale/tk/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/tr') recursedown('./django/contrib/sessions/locale/tr/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/tt') recursedown('./django/contrib/sessions/locale/tt/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/udm') recursedown('./django/contrib/sessions/locale/udm/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ug') recursedown('./django/contrib/sessions/locale/ug/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/uk') recursedown('./django/contrib/sessions/locale/uk/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/ur') recursedown('./django/contrib/sessions/locale/ur/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/uz') recursedown('./django/contrib/sessions/locale/uz/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/vi') recursedown('./django/contrib/sessions/locale/vi/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/zh_Hans') recursedown('./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/sessions/locale/zh_Hant') recursedown('./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/sessions/management') recursedown('./django/contrib/sessions/management/commands') recursedown('./django/contrib/sessions/migrations') recursedown('./django/contrib/sitemaps') recursedown('./django/contrib/sitemaps/templates') recursedown('./django/contrib/sites') recursedown('./django/contrib/sites/locale') recursedown('./django/contrib/sites/locale/af') recursedown('./django/contrib/sites/locale/af/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ar') recursedown('./django/contrib/sites/locale/ar/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ar_DZ') recursedown('./django/contrib/sites/locale/ar_DZ/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ast') recursedown('./django/contrib/sites/locale/ast/LC_MESSAGES') recursedown('./django/contrib/sites/locale/az') recursedown('./django/contrib/sites/locale/az/LC_MESSAGES') recursedown('./django/contrib/sites/locale/be') recursedown('./django/contrib/sites/locale/be/LC_MESSAGES') recursedown('./django/contrib/sites/locale/bg') recursedown('./django/contrib/sites/locale/bg/LC_MESSAGES') recursedown('./django/contrib/sites/locale/bn') recursedown('./django/contrib/sites/locale/bn/LC_MESSAGES') recursedown('./django/contrib/sites/locale/br') recursedown('./django/contrib/sites/locale/br/LC_MESSAGES') recursedown('./django/contrib/sites/locale/bs') recursedown('./django/contrib/sites/locale/bs/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ca') recursedown('./django/contrib/sites/locale/ca/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ckb') recursedown('./django/contrib/sites/locale/ckb/LC_MESSAGES') recursedown('./django/contrib/sites/locale/cs') recursedown('./django/contrib/sites/locale/cs/LC_MESSAGES') recursedown('./django/contrib/sites/locale/cy') recursedown('./django/contrib/sites/locale/cy/LC_MESSAGES') recursedown('./django/contrib/sites/locale/da') recursedown('./django/contrib/sites/locale/da/LC_MESSAGES') recursedown('./django/contrib/sites/locale/de') recursedown('./django/contrib/sites/locale/de/LC_MESSAGES') recursedown('./django/contrib/sites/locale/dsb') recursedown('./django/contrib/sites/locale/dsb/LC_MESSAGES') recursedown('./django/contrib/sites/locale/el') recursedown('./django/contrib/sites/locale/el/LC_MESSAGES') recursedown('./django/contrib/sites/locale/en') recursedown('./django/contrib/sites/locale/en/LC_MESSAGES') recursedown('./django/contrib/sites/locale/en_AU') recursedown('./django/contrib/sites/locale/en_AU/LC_MESSAGES') recursedown('./django/contrib/sites/locale/en_GB') recursedown('./django/contrib/sites/locale/en_GB/LC_MESSAGES') recursedown('./django/contrib/sites/locale/eo') recursedown('./django/contrib/sites/locale/eo/LC_MESSAGES') recursedown('./django/contrib/sites/locale/es') recursedown('./django/contrib/sites/locale/es/LC_MESSAGES') recursedown('./django/contrib/sites/locale/es_AR') recursedown('./django/contrib/sites/locale/es_AR/LC_MESSAGES') recursedown('./django/contrib/sites/locale/es_CO') recursedown('./django/contrib/sites/locale/es_CO/LC_MESSAGES') recursedown('./django/contrib/sites/locale/es_MX') recursedown('./django/contrib/sites/locale/es_MX/LC_MESSAGES') recursedown('./django/contrib/sites/locale/es_VE') recursedown('./django/contrib/sites/locale/es_VE/LC_MESSAGES') recursedown('./django/contrib/sites/locale/et') recursedown('./django/contrib/sites/locale/et/LC_MESSAGES') recursedown('./django/contrib/sites/locale/eu') recursedown('./django/contrib/sites/locale/eu/LC_MESSAGES') recursedown('./django/contrib/sites/locale/fa') recursedown('./django/contrib/sites/locale/fa/LC_MESSAGES') recursedown('./django/contrib/sites/locale/fi') recursedown('./django/contrib/sites/locale/fi/LC_MESSAGES') recursedown('./django/contrib/sites/locale/fr') recursedown('./django/contrib/sites/locale/fr/LC_MESSAGES') recursedown('./django/contrib/sites/locale/fy') recursedown('./django/contrib/sites/locale/fy/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ga') recursedown('./django/contrib/sites/locale/ga/LC_MESSAGES') recursedown('./django/contrib/sites/locale/gd') recursedown('./django/contrib/sites/locale/gd/LC_MESSAGES') recursedown('./django/contrib/sites/locale/gl') recursedown('./django/contrib/sites/locale/gl/LC_MESSAGES') recursedown('./django/contrib/sites/locale/he') recursedown('./django/contrib/sites/locale/he/LC_MESSAGES') recursedown('./django/contrib/sites/locale/hi') recursedown('./django/contrib/sites/locale/hi/LC_MESSAGES') recursedown('./django/contrib/sites/locale/hr') recursedown('./django/contrib/sites/locale/hr/LC_MESSAGES') recursedown('./django/contrib/sites/locale/hsb') recursedown('./django/contrib/sites/locale/hsb/LC_MESSAGES') recursedown('./django/contrib/sites/locale/hu') recursedown('./django/contrib/sites/locale/hu/LC_MESSAGES') recursedown('./django/contrib/sites/locale/hy') recursedown('./django/contrib/sites/locale/hy/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ia') recursedown('./django/contrib/sites/locale/ia/LC_MESSAGES') recursedown('./django/contrib/sites/locale/id') recursedown('./django/contrib/sites/locale/id/LC_MESSAGES') recursedown('./django/contrib/sites/locale/io') recursedown('./django/contrib/sites/locale/io/LC_MESSAGES') recursedown('./django/contrib/sites/locale/is') recursedown('./django/contrib/sites/locale/is/LC_MESSAGES') recursedown('./django/contrib/sites/locale/it') recursedown('./django/contrib/sites/locale/it/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ja') recursedown('./django/contrib/sites/locale/ja/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ka') recursedown('./django/contrib/sites/locale/ka/LC_MESSAGES') recursedown('./django/contrib/sites/locale/kab') recursedown('./django/contrib/sites/locale/kab/LC_MESSAGES') recursedown('./django/contrib/sites/locale/kk') recursedown('./django/contrib/sites/locale/kk/LC_MESSAGES') recursedown('./django/contrib/sites/locale/km') recursedown('./django/contrib/sites/locale/km/LC_MESSAGES') recursedown('./django/contrib/sites/locale/kn') recursedown('./django/contrib/sites/locale/kn/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ko') recursedown('./django/contrib/sites/locale/ko/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ky') recursedown('./django/contrib/sites/locale/ky/LC_MESSAGES') recursedown('./django/contrib/sites/locale/lb') recursedown('./django/contrib/sites/locale/lb/LC_MESSAGES') recursedown('./django/contrib/sites/locale/lt') recursedown('./django/contrib/sites/locale/lt/LC_MESSAGES') recursedown('./django/contrib/sites/locale/lv') recursedown('./django/contrib/sites/locale/lv/LC_MESSAGES') recursedown('./django/contrib/sites/locale/mk') recursedown('./django/contrib/sites/locale/mk/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ml') recursedown('./django/contrib/sites/locale/ml/LC_MESSAGES') recursedown('./django/contrib/sites/locale/mn') recursedown('./django/contrib/sites/locale/mn/LC_MESSAGES') recursedown('./django/contrib/sites/locale/mr') recursedown('./django/contrib/sites/locale/mr/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ms') recursedown('./django/contrib/sites/locale/ms/LC_MESSAGES') recursedown('./django/contrib/sites/locale/my') recursedown('./django/contrib/sites/locale/my/LC_MESSAGES') recursedown('./django/contrib/sites/locale/nb') recursedown('./django/contrib/sites/locale/nb/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ne') recursedown('./django/contrib/sites/locale/ne/LC_MESSAGES') recursedown('./django/contrib/sites/locale/nl') recursedown('./django/contrib/sites/locale/nl/LC_MESSAGES') recursedown('./django/contrib/sites/locale/nn') recursedown('./django/contrib/sites/locale/nn/LC_MESSAGES') recursedown('./django/contrib/sites/locale/os') recursedown('./django/contrib/sites/locale/os/LC_MESSAGES') recursedown('./django/contrib/sites/locale/pa') recursedown('./django/contrib/sites/locale/pa/LC_MESSAGES') recursedown('./django/contrib/sites/locale/pl') recursedown('./django/contrib/sites/locale/pl/LC_MESSAGES') recursedown('./django/contrib/sites/locale/pt') recursedown('./django/contrib/sites/locale/pt/LC_MESSAGES') recursedown('./django/contrib/sites/locale/pt_BR') recursedown('./django/contrib/sites/locale/pt_BR/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ro') recursedown('./django/contrib/sites/locale/ro/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ru') recursedown('./django/contrib/sites/locale/ru/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sk') recursedown('./django/contrib/sites/locale/sk/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sl') recursedown('./django/contrib/sites/locale/sl/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sq') recursedown('./django/contrib/sites/locale/sq/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sr') recursedown('./django/contrib/sites/locale/sr/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sr_Latn') recursedown('./django/contrib/sites/locale/sr_Latn/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sv') recursedown('./django/contrib/sites/locale/sv/LC_MESSAGES') recursedown('./django/contrib/sites/locale/sw') recursedown('./django/contrib/sites/locale/sw/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ta') recursedown('./django/contrib/sites/locale/ta/LC_MESSAGES') recursedown('./django/contrib/sites/locale/te') recursedown('./django/contrib/sites/locale/te/LC_MESSAGES') recursedown('./django/contrib/sites/locale/tg') recursedown('./django/contrib/sites/locale/tg/LC_MESSAGES') recursedown('./django/contrib/sites/locale/th') recursedown('./django/contrib/sites/locale/th/LC_MESSAGES') recursedown('./django/contrib/sites/locale/tk') recursedown('./django/contrib/sites/locale/tk/LC_MESSAGES') recursedown('./django/contrib/sites/locale/tr') recursedown('./django/contrib/sites/locale/tr/LC_MESSAGES') recursedown('./django/contrib/sites/locale/tt') recursedown('./django/contrib/sites/locale/tt/LC_MESSAGES') recursedown('./django/contrib/sites/locale/udm') recursedown('./django/contrib/sites/locale/udm/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ug') recursedown('./django/contrib/sites/locale/ug/LC_MESSAGES') recursedown('./django/contrib/sites/locale/uk') recursedown('./django/contrib/sites/locale/uk/LC_MESSAGES') recursedown('./django/contrib/sites/locale/ur') recursedown('./django/contrib/sites/locale/ur/LC_MESSAGES') recursedown('./django/contrib/sites/locale/uz') recursedown('./django/contrib/sites/locale/uz/LC_MESSAGES') recursedown('./django/contrib/sites/locale/vi') recursedown('./django/contrib/sites/locale/vi/LC_MESSAGES') recursedown('./django/contrib/sites/locale/zh_Hans') recursedown('./django/contrib/sites/locale/zh_Hans/LC_MESSAGES') recursedown('./django/contrib/sites/locale/zh_Hant') recursedown('./django/contrib/sites/locale/zh_Hant/LC_MESSAGES') recursedown('./django/contrib/sites/migrations') recursedown('./django/contrib/staticfiles') recursedown('./django/contrib/staticfiles/management') recursedown('./django/contrib/staticfiles/management/commands') recursedown('./django/contrib/syndication') recursedown('./django/core') recursedown('./django/core/cache') recursedown('./django/core/cache/backends') recursedown('./django/core/checks') recursedown('./django/core/checks/compatibility') recursedown('./django/core/checks/security') recursedown('./django/core/files') recursedown('./django/core/files/storage') recursedown('./django/core/handlers') recursedown('./django/core/mail') recursedown('./django/core/mail/backends') recursedown('./django/core/management') recursedown('./django/core/management/commands') recursedown('./django/core/serializers') recursedown('./django/core/servers') recursedown('./django/db') recursedown('./django/db/backends') recursedown('./django/db/backends/base') recursedown('./django/db/backends/dummy') recursedown('./django/db/backends/mysql') recursedown('./django/db/backends/oracle') recursedown('./django/db/backends/postgresql') recursedown('./django/db/backends/sqlite3') recursedown('./django/db/migrations') recursedown('./django/db/migrations/operations') recursedown('./django/db/models') recursedown('./django/db/models/fields') recursedown('./django/db/models/functions') recursedown('./django/db/models/sql') recursedown('./django/dispatch') recursedown('./django/forms') recursedown('./django/forms/jinja2') recursedown('./django/forms/jinja2/django') recursedown('./django/forms/jinja2/django/forms') recursedown('./django/forms/jinja2/django/forms/errors') recursedown('./django/forms/jinja2/django/forms/errors/dict') recursedown('./django/forms/jinja2/django/forms/errors/list') recursedown('./django/forms/jinja2/django/forms/formsets') recursedown('./django/forms/jinja2/django/forms/widgets') recursedown('./django/forms/templates') recursedown('./django/forms/templates/django') recursedown('./django/forms/templates/django/forms') recursedown('./django/forms/templates/django/forms/errors') recursedown('./django/forms/templates/django/forms/errors/dict') recursedown('./django/forms/templates/django/forms/errors/list') recursedown('./django/forms/templates/django/forms/formsets') recursedown('./django/forms/templates/django/forms/widgets') recursedown('./django/http') recursedown('./django/middleware') recursedown('./django/template') recursedown('./django/template/backends') recursedown('./django/template/loaders') recursedown('./django/templatetags') recursedown('./django/test') recursedown('./django/urls') recursedown('./django/utils') recursedown('./django/utils/translation') recursedown('./django/views') recursedown('./django/views/decorators') recursedown('./django/views/generic') recursedown('./django/views/templates') recursedown('./docs') recursedown('./docs/_ext') recursedown('./docs/_theme') recursedown('./docs/_theme/djangodocs') recursedown('./docs/_theme/djangodocs/static') recursedown('./docs/_theme/djangodocs/static/fontawesome') recursedown('./docs/_theme/djangodocs/static/fontawesome/css') recursedown('./docs/_theme/djangodocs/static/fontawesome/webfonts') recursedown('./docs/_theme/djangodocs-epub') recursedown('./docs/_theme/djangodocs-epub/static') recursedown('./docs/faq') recursedown('./docs/howto') recursedown('./docs/howto/_images') recursedown('./docs/howto/deployment') recursedown('./docs/howto/deployment/asgi') recursedown('./docs/howto/deployment/wsgi') recursedown('./docs/howto/static-files') recursedown('./docs/internals') recursedown('./docs/internals/_images') recursedown('./docs/internals/contributing') recursedown('./docs/internals/contributing/writing-code') recursedown('./docs/intro') recursedown('./docs/intro/_images') recursedown('./docs/man') recursedown('./docs/misc') recursedown('./docs/ref') recursedown('./docs/ref/class-based-views') recursedown('./docs/ref/contrib') recursedown('./docs/ref/contrib/admin') recursedown('./docs/ref/contrib/admin/_images') recursedown('./docs/ref/contrib/gis') recursedown('./docs/ref/contrib/gis/install') recursedown('./docs/ref/contrib/postgres') recursedown('./docs/ref/files') recursedown('./docs/ref/forms') recursedown('./docs/ref/models') recursedown('./docs/ref/templates') recursedown('./docs/releases') recursedown('./docs/topics') recursedown('./docs/topics/auth') recursedown('./docs/topics/class-based-views') recursedown('./docs/topics/db') recursedown('./docs/topics/db/examples') recursedown('./docs/topics/forms') recursedown('./docs/topics/http') recursedown('./docs/topics/http/_images') recursedown('./docs/topics/i18n') recursedown('./docs/topics/testing') recursedown('./docs/topics/testing/_images') recursedown('./extras') recursedown('./js_tests') recursedown('./js_tests/admin') recursedown('./js_tests/gis') recursedown('./scripts') recursedown('./tests') recursedown('./tests/absolute_url_overrides') recursedown('./tests/admin_autodiscover') recursedown('./tests/admin_changelist') recursedown('./tests/admin_checks') recursedown('./tests/admin_custom_urls') recursedown('./tests/admin_default_site') recursedown('./tests/admin_docs') recursedown('./tests/admin_filters') recursedown('./tests/admin_inlines') recursedown('./tests/admin_ordering') recursedown('./tests/admin_registration') recursedown('./tests/admin_scripts') recursedown('./tests/admin_scripts/another_app_waiting_migration') recursedown('./tests/admin_scripts/another_app_waiting_migration/migrations') recursedown('./tests/admin_scripts/app_raising_messages') recursedown('./tests/admin_scripts/app_raising_warning') recursedown('./tests/admin_scripts/app_waiting_migration') recursedown('./tests/admin_scripts/app_waiting_migration/migrations') recursedown('./tests/admin_scripts/app_with_import') recursedown('./tests/admin_scripts/broken_app') recursedown('./tests/admin_scripts/complex_app') recursedown('./tests/admin_scripts/complex_app/admin') recursedown('./tests/admin_scripts/complex_app/management') recursedown('./tests/admin_scripts/complex_app/management/commands') recursedown('./tests/admin_scripts/complex_app/models') recursedown('./tests/admin_scripts/custom_templates') recursedown('./tests/admin_scripts/custom_templates/app_template') recursedown('./tests/admin_scripts/custom_templates/project_template') recursedown('./tests/admin_scripts/custom_templates/project_template/.hidden') recursedown('./tests/admin_scripts/custom_templates/project_template/additional_dir') recursedown('./tests/admin_scripts/custom_templates/project_template/project_name') recursedown('./tests/admin_scripts/management') recursedown('./tests/admin_scripts/management/commands') recursedown('./tests/admin_scripts/simple_app') recursedown('./tests/admin_scripts/simple_app/management') recursedown('./tests/admin_scripts/simple_app/management/commands') recursedown('./tests/admin_utils') recursedown('./tests/admin_views') recursedown('./tests/admin_views/templates') recursedown('./tests/admin_views/templates/admin') recursedown('./tests/admin_views/templates/admin/admin_views') recursedown('./tests/admin_views/templates/admin/admin_views/article') recursedown('./tests/admin_widgets') recursedown('./tests/aggregation') recursedown('./tests/aggregation_regress') recursedown('./tests/annotations') recursedown('./tests/app_loading') recursedown('./tests/app_loading/eggs') recursedown('./tests/app_loading/not_installed') recursedown('./tests/apps') recursedown('./tests/apps/namespace_package_base') recursedown('./tests/apps/namespace_package_base/nsapp') recursedown('./tests/apps/namespace_package_other_base') recursedown('./tests/apps/namespace_package_other_base/nsapp') recursedown('./tests/apps/no_config_app') recursedown('./tests/apps/one_config_app') recursedown('./tests/apps/query_performing_app') recursedown('./tests/apps/two_configs_app') recursedown('./tests/apps/two_configs_one_default_app') recursedown('./tests/apps/two_default_configs_app') recursedown('./tests/asgi') recursedown('./tests/asgi/project') recursedown('./tests/asgi/project/static') recursedown('./tests/async') recursedown('./tests/auth_tests') recursedown('./tests/auth_tests/fixtures') recursedown('./tests/auth_tests/models') recursedown('./tests/auth_tests/templates') recursedown('./tests/auth_tests/templates/context_processors') recursedown('./tests/auth_tests/templates/registration') recursedown('./tests/backends') recursedown('./tests/backends/base') recursedown('./tests/backends/base/app_unmigrated') recursedown('./tests/backends/base/app_unmigrated/migrations') recursedown('./tests/backends/mysql') recursedown('./tests/backends/oracle') recursedown('./tests/backends/postgresql') recursedown('./tests/backends/sqlite') recursedown('./tests/base') recursedown('./tests/bash_completion') recursedown('./tests/bash_completion/management') recursedown('./tests/bash_completion/management/commands') recursedown('./tests/basic') recursedown('./tests/builtin_server') recursedown('./tests/bulk_create') recursedown('./tests/cache') recursedown('./tests/check_framework') recursedown('./tests/check_framework/template_test_apps') recursedown('./tests/check_framework/template_test_apps/different_tags_app') recursedown('./tests/check_framework/template_test_apps/different_tags_app/templatetags') recursedown('./tests/check_framework/template_test_apps/same_tags_app_1') recursedown('./tests/check_framework/template_test_apps/same_tags_app_1/templatetags') recursedown('./tests/check_framework/template_test_apps/same_tags_app_2') recursedown('./tests/check_framework/template_test_apps/same_tags_app_2/templatetags') recursedown('./tests/check_framework/urls') recursedown('./tests/check_framework/urls/path_compatibility') recursedown('./tests/conditional_processing') recursedown('./tests/constraints') recursedown('./tests/contenttypes_tests') recursedown('./tests/contenttypes_tests/operations_migrations') recursedown('./tests/context_processors') recursedown('./tests/context_processors/templates') recursedown('./tests/context_processors/templates/context_processors') recursedown('./tests/csrf_tests') recursedown('./tests/custom_columns') recursedown('./tests/custom_lookups') recursedown('./tests/custom_managers') recursedown('./tests/custom_methods') recursedown('./tests/custom_migration_operations') recursedown('./tests/custom_pk') recursedown('./tests/datatypes') recursedown('./tests/dates') recursedown('./tests/datetimes') recursedown('./tests/db_functions') recursedown('./tests/db_functions/comparison') recursedown('./tests/db_functions/datetime') recursedown('./tests/db_functions/math') recursedown('./tests/db_functions/migrations') recursedown('./tests/db_functions/text') recursedown('./tests/db_functions/window') recursedown('./tests/db_typecasts') recursedown('./tests/db_utils') recursedown('./tests/dbshell') recursedown('./tests/decorators') recursedown('./tests/defer') recursedown('./tests/defer_regress') recursedown('./tests/delete') recursedown('./tests/delete_regress') recursedown('./tests/deprecation') recursedown('./tests/dispatch') recursedown('./tests/distinct_on_fields') recursedown('./tests/empty') recursedown('./tests/empty/no_models') recursedown('./tests/empty_models') recursedown('./tests/expressions') recursedown('./tests/expressions_case') recursedown('./tests/expressions_window') recursedown('./tests/extra_regress') recursedown('./tests/field_deconstruction') recursedown('./tests/field_defaults') recursedown('./tests/field_subclassing') recursedown('./tests/file_storage') recursedown('./tests/file_uploads') recursedown('./tests/files') recursedown('./tests/filtered_relation') recursedown('./tests/fixtures') recursedown('./tests/fixtures/fixtures') recursedown('./tests/fixtures_model_package') recursedown('./tests/fixtures_model_package/fixtures') recursedown('./tests/fixtures_model_package/models') recursedown('./tests/fixtures_regress') recursedown('./tests/fixtures_regress/fixtures') recursedown('./tests/fixtures_regress/fixtures_1') recursedown('./tests/fixtures_regress/fixtures_1/inner') recursedown('./tests/fixtures_regress/fixtures_2') recursedown('./tests/flatpages_tests') recursedown('./tests/flatpages_tests/templates') recursedown('./tests/flatpages_tests/templates/flatpages') recursedown('./tests/flatpages_tests/templates/registration') recursedown('./tests/force_insert_update') recursedown('./tests/foreign_object') recursedown('./tests/foreign_object/models') recursedown('./tests/forms_tests') recursedown('./tests/forms_tests/field_tests') recursedown('./tests/forms_tests/field_tests/filepathfield_test_dir') recursedown('./tests/forms_tests/field_tests/filepathfield_test_dir/c') recursedown('./tests/forms_tests/field_tests/filepathfield_test_dir/c/f') recursedown('./tests/forms_tests/field_tests/filepathfield_test_dir/h') recursedown('./tests/forms_tests/field_tests/filepathfield_test_dir/j') recursedown('./tests/forms_tests/jinja2') recursedown('./tests/forms_tests/jinja2/forms_tests') recursedown('./tests/forms_tests/templates') recursedown('./tests/forms_tests/templates/forms_tests') recursedown('./tests/forms_tests/templatetags') recursedown('./tests/forms_tests/tests') recursedown('./tests/forms_tests/tests/filepath_test_files') recursedown('./tests/forms_tests/tests/filepath_test_files/directory') recursedown('./tests/forms_tests/widget_tests') recursedown('./tests/from_db_value') recursedown('./tests/generic_inline_admin') recursedown('./tests/generic_relations') recursedown('./tests/generic_relations_regress') recursedown('./tests/generic_views') recursedown('./tests/generic_views/jinja2') recursedown('./tests/generic_views/jinja2/generic_views') recursedown('./tests/generic_views/templates') recursedown('./tests/generic_views/templates/generic_views') recursedown('./tests/generic_views/templates/registration') recursedown('./tests/get_earliest_or_latest') recursedown('./tests/get_object_or_404') recursedown('./tests/get_or_create') recursedown('./tests/gis_tests') recursedown('./tests/gis_tests/data') recursedown('./tests/gis_tests/data/ch-city') recursedown('./tests/gis_tests/data/cities') recursedown('./tests/gis_tests/data/counties') recursedown('./tests/gis_tests/data/gas_lines') recursedown('./tests/gis_tests/data/has_nulls') recursedown('./tests/gis_tests/data/interstates') recursedown('./tests/gis_tests/data/invalid') recursedown('./tests/gis_tests/data/rasters') recursedown('./tests/gis_tests/data/test_point') recursedown('./tests/gis_tests/data/test_poly') recursedown('./tests/gis_tests/data/test_vrt') recursedown('./tests/gis_tests/distapp') recursedown('./tests/gis_tests/distapp/fixtures') recursedown('./tests/gis_tests/gdal_tests') recursedown('./tests/gis_tests/geo3d') recursedown('./tests/gis_tests/geoadmin') recursedown('./tests/gis_tests/geoapp') recursedown('./tests/gis_tests/geoapp/fixtures') recursedown('./tests/gis_tests/geogapp') recursedown('./tests/gis_tests/geogapp/fixtures') recursedown('./tests/gis_tests/geos_tests') recursedown('./tests/gis_tests/gis_migrations') recursedown('./tests/gis_tests/gis_migrations/migrations') recursedown('./tests/gis_tests/inspectapp') recursedown('./tests/gis_tests/layermap') recursedown('./tests/gis_tests/rasterapp') recursedown('./tests/gis_tests/rasterapp/migrations') recursedown('./tests/gis_tests/relatedapp') recursedown('./tests/gis_tests/relatedapp/fixtures') recursedown('./tests/handlers') recursedown('./tests/handlers/templates') recursedown('./tests/httpwrappers') recursedown('./tests/humanize_tests') recursedown('./tests/i18n') recursedown('./tests/i18n/commands') recursedown('./tests/i18n/commands/app_with_locale') recursedown('./tests/i18n/commands/app_with_locale/locale') recursedown('./tests/i18n/commands/app_with_locale/locale/ru') recursedown('./tests/i18n/commands/app_with_locale/locale/ru/LC_MESSAGES') recursedown('./tests/i18n/commands/ignore_dir') recursedown('./tests/i18n/commands/locale') recursedown('./tests/i18n/commands/locale/en') recursedown('./tests/i18n/commands/locale/en/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/es_AR') recursedown('./tests/i18n/commands/locale/es_AR/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/fr') recursedown('./tests/i18n/commands/locale/fr/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/hr') recursedown('./tests/i18n/commands/locale/hr/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/ja') recursedown('./tests/i18n/commands/locale/ja/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/ko') recursedown('./tests/i18n/commands/locale/ko/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/pt_BR') recursedown('./tests/i18n/commands/locale/pt_BR/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/ru') recursedown('./tests/i18n/commands/locale/ru/LC_MESSAGES') recursedown('./tests/i18n/commands/locale/xxx') recursedown('./tests/i18n/commands/locale/xxx/LC_MESSAGES') recursedown('./tests/i18n/commands/media_root') recursedown('./tests/i18n/commands/someapp') recursedown('./tests/i18n/commands/someapp/static') recursedown('./tests/i18n/commands/static') recursedown('./tests/i18n/commands/templates') recursedown('./tests/i18n/commands/templates/subdir') recursedown('./tests/i18n/contenttypes') recursedown('./tests/i18n/contenttypes/locale') recursedown('./tests/i18n/contenttypes/locale/en') recursedown('./tests/i18n/contenttypes/locale/en/LC_MESSAGES') recursedown('./tests/i18n/contenttypes/locale/fr') recursedown('./tests/i18n/contenttypes/locale/fr/LC_MESSAGES') recursedown('./tests/i18n/exclude') recursedown('./tests/i18n/exclude/canned_locale') recursedown('./tests/i18n/exclude/canned_locale/en') recursedown('./tests/i18n/exclude/canned_locale/en/LC_MESSAGES') recursedown('./tests/i18n/exclude/canned_locale/fr') recursedown('./tests/i18n/exclude/canned_locale/fr/LC_MESSAGES') recursedown('./tests/i18n/exclude/canned_locale/it') recursedown('./tests/i18n/exclude/canned_locale/it/LC_MESSAGES') recursedown('./tests/i18n/loading') recursedown('./tests/i18n/loading/en') recursedown('./tests/i18n/loading/en/LC_MESSAGES') recursedown('./tests/i18n/loading/en_AU') recursedown('./tests/i18n/loading/en_AU/LC_MESSAGES') recursedown('./tests/i18n/loading/en_CA') recursedown('./tests/i18n/loading/en_CA/LC_MESSAGES') recursedown('./tests/i18n/loading/en_NZ') recursedown('./tests/i18n/loading/en_NZ/LC_MESSAGES') recursedown('./tests/i18n/loading_app') recursedown('./tests/i18n/loading_app/locale') recursedown('./tests/i18n/loading_app/locale/en') recursedown('./tests/i18n/loading_app/locale/en/LC_MESSAGES') recursedown('./tests/i18n/obsolete_translations') recursedown('./tests/i18n/obsolete_translations/locale') recursedown('./tests/i18n/obsolete_translations/locale/de') recursedown('./tests/i18n/obsolete_translations/locale/de/LC_MESSAGES') recursedown('./tests/i18n/other') recursedown('./tests/i18n/other/locale') recursedown('./tests/i18n/other/locale/de') recursedown('./tests/i18n/other/locale/de/LC_MESSAGES') recursedown('./tests/i18n/other/locale/fr') recursedown('./tests/i18n/other/locale/fr/LC_MESSAGES') recursedown('./tests/i18n/other2') recursedown('./tests/i18n/other2/locale') recursedown('./tests/i18n/other2/locale/de') recursedown('./tests/i18n/patterns') recursedown('./tests/i18n/patterns/locale') recursedown('./tests/i18n/patterns/locale/en') recursedown('./tests/i18n/patterns/locale/en/LC_MESSAGES') recursedown('./tests/i18n/patterns/locale/nl') recursedown('./tests/i18n/patterns/locale/nl/LC_MESSAGES') recursedown('./tests/i18n/patterns/locale/pt_BR') recursedown('./tests/i18n/patterns/locale/pt_BR/LC_MESSAGES') recursedown('./tests/i18n/patterns/templates') recursedown('./tests/i18n/patterns/urls') recursedown('./tests/i18n/project_dir') recursedown('./tests/i18n/project_dir/app_no_locale') recursedown('./tests/i18n/project_dir/app_with_locale') recursedown('./tests/i18n/project_dir/app_with_locale/locale') recursedown('./tests/i18n/project_dir/project_locale') recursedown('./tests/i18n/resolution') recursedown('./tests/i18n/resolution/locale') recursedown('./tests/i18n/resolution/locale/de') recursedown('./tests/i18n/resolution/locale/de/LC_MESSAGES') recursedown('./tests/i18n/sampleproject') recursedown('./tests/i18n/sampleproject/locale') recursedown('./tests/i18n/sampleproject/locale/fr') recursedown('./tests/i18n/sampleproject/locale/fr/LC_MESSAGES') recursedown('./tests/i18n/sampleproject/sampleproject') recursedown('./tests/i18n/sampleproject/templates') recursedown('./tests/i18n/territorial_fallback') recursedown('./tests/i18n/territorial_fallback/locale') recursedown('./tests/i18n/territorial_fallback/locale/de') recursedown('./tests/i18n/territorial_fallback/locale/de/LC_MESSAGES') recursedown('./tests/i18n/territorial_fallback/locale/de_DE') recursedown('./tests/i18n/territorial_fallback/locale/de_DE/LC_MESSAGES') recursedown('./tests/i18n/unchanged') recursedown('./tests/i18n/unchanged/locale') recursedown('./tests/i18n/unchanged/locale/de') recursedown('./tests/i18n/unchanged/locale/de/LC_MESSAGES') recursedown('./tests/import_error_package') recursedown('./tests/indexes') recursedown('./tests/inline_formsets') recursedown('./tests/inspectdb') recursedown('./tests/introspection') recursedown('./tests/invalid_models_tests') recursedown('./tests/known_related_objects') recursedown('./tests/logging_tests') recursedown('./tests/lookup') recursedown('./tests/m2m_and_m2o') recursedown('./tests/m2m_intermediary') recursedown('./tests/m2m_multiple') recursedown('./tests/m2m_recursive') recursedown('./tests/m2m_regress') recursedown('./tests/m2m_signals') recursedown('./tests/m2m_through') recursedown('./tests/m2m_through_regress') recursedown('./tests/m2m_through_regress/fixtures') recursedown('./tests/m2o_recursive') recursedown('./tests/mail') recursedown('./tests/mail/attachments') recursedown('./tests/managers_regress') recursedown('./tests/many_to_many') recursedown('./tests/many_to_one') recursedown('./tests/many_to_one_null') recursedown('./tests/max_lengths') recursedown('./tests/messages_tests') recursedown('./tests/middleware') recursedown('./tests/middleware_exceptions') recursedown('./tests/migrate_signals') recursedown('./tests/migrate_signals/custom_migrations') recursedown('./tests/migration_test_data_persistence') recursedown('./tests/migration_test_data_persistence/migrations') recursedown('./tests/migrations') recursedown('./tests/migrations/deprecated_field_migrations') recursedown('./tests/migrations/faulty_migrations') recursedown('./tests/migrations/faulty_migrations/namespace') recursedown('./tests/migrations/faulty_migrations/namespace/foo') recursedown('./tests/migrations/migrations_test_apps') recursedown('./tests/migrations/migrations_test_apps/alter_fk') recursedown('./tests/migrations/migrations_test_apps/alter_fk/author_app') recursedown('./tests/migrations/migrations_test_apps/alter_fk/author_app/migrations') recursedown('./tests/migrations/migrations_test_apps/alter_fk/book_app') recursedown('./tests/migrations/migrations_test_apps/alter_fk/book_app/migrations') recursedown('./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies') recursedown('./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies/migrations') recursedown('./tests/migrations/migrations_test_apps/lookuperror_a') recursedown('./tests/migrations/migrations_test_apps/lookuperror_a/migrations') recursedown('./tests/migrations/migrations_test_apps/lookuperror_b') recursedown('./tests/migrations/migrations_test_apps/lookuperror_b/migrations') recursedown('./tests/migrations/migrations_test_apps/lookuperror_c') recursedown('./tests/migrations/migrations_test_apps/lookuperror_c/migrations') recursedown('./tests/migrations/migrations_test_apps/migrated_app') recursedown('./tests/migrations/migrations_test_apps/migrated_app/migrations') recursedown('./tests/migrations/migrations_test_apps/migrated_unapplied_app') recursedown('./tests/migrations/migrations_test_apps/migrated_unapplied_app/migrations') recursedown('./tests/migrations/migrations_test_apps/mutate_state_a') recursedown('./tests/migrations/migrations_test_apps/mutate_state_a/migrations') recursedown('./tests/migrations/migrations_test_apps/mutate_state_b') recursedown('./tests/migrations/migrations_test_apps/mutate_state_b/migrations') recursedown('./tests/migrations/migrations_test_apps/normal') recursedown('./tests/migrations/migrations_test_apps/unmigrated_app') recursedown('./tests/migrations/migrations_test_apps/unmigrated_app_simple') recursedown('./tests/migrations/migrations_test_apps/unmigrated_app_syncdb') recursedown('./tests/migrations/migrations_test_apps/unspecified_app_with_conflict') recursedown('./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/migrations') recursedown('./tests/migrations/migrations_test_apps/with_package_model') recursedown('./tests/migrations/migrations_test_apps/with_package_model/models') recursedown('./tests/migrations/migrations_test_apps/without_init_file') recursedown('./tests/migrations/migrations_test_apps/without_init_file/migrations') recursedown('./tests/migrations/related_models_app') recursedown('./tests/migrations/test_add_many_to_many_field_initial') recursedown('./tests/migrations/test_auto_now_add') recursedown('./tests/migrations/test_fake_initial_case_insensitive') recursedown('./tests/migrations/test_fake_initial_case_insensitive/fake_initial') recursedown('./tests/migrations/test_fake_initial_case_insensitive/initial') recursedown('./tests/migrations/test_migrations') recursedown('./tests/migrations/test_migrations_atomic_operation') recursedown('./tests/migrations/test_migrations_backwards_deps_1') recursedown('./tests/migrations/test_migrations_bad_pyc') recursedown('./tests/migrations/test_migrations_clashing_prefix') recursedown('./tests/migrations/test_migrations_conflict') recursedown('./tests/migrations/test_migrations_conflict_long_name') recursedown('./tests/migrations/test_migrations_custom_user') recursedown('./tests/migrations/test_migrations_empty') recursedown('./tests/migrations/test_migrations_fake_split_initial') recursedown('./tests/migrations/test_migrations_first') recursedown('./tests/migrations/test_migrations_initial_false') recursedown('./tests/migrations/test_migrations_manual_porting') recursedown('./tests/migrations/test_migrations_namespace_package') recursedown('./tests/migrations/test_migrations_no_ancestor') recursedown('./tests/migrations/test_migrations_no_changes') recursedown('./tests/migrations/test_migrations_no_default') recursedown('./tests/migrations/test_migrations_no_init') recursedown('./tests/migrations/test_migrations_no_operations') recursedown('./tests/migrations/test_migrations_non_atomic') recursedown('./tests/migrations/test_migrations_noop') recursedown('./tests/migrations/test_migrations_order') recursedown('./tests/migrations/test_migrations_plan') recursedown('./tests/migrations/test_migrations_private') recursedown('./tests/migrations/test_migrations_run_before') recursedown('./tests/migrations/test_migrations_squashed') recursedown('./tests/migrations/test_migrations_squashed_complex') recursedown('./tests/migrations/test_migrations_squashed_complex_multi_apps') recursedown('./tests/migrations/test_migrations_squashed_complex_multi_apps/app1') recursedown('./tests/migrations/test_migrations_squashed_complex_multi_apps/app2') recursedown('./tests/migrations/test_migrations_squashed_erroneous') recursedown('./tests/migrations/test_migrations_squashed_extra') recursedown('./tests/migrations/test_migrations_squashed_no_replaces') recursedown('./tests/migrations/test_migrations_squashed_ref_squashed') recursedown('./tests/migrations/test_migrations_squashed_ref_squashed/app1') recursedown('./tests/migrations/test_migrations_squashed_ref_squashed/app2') recursedown('./tests/migrations/test_migrations_unmigdep') recursedown('./tests/migrations2') recursedown('./tests/migrations2/test_migrations_2') recursedown('./tests/migrations2/test_migrations_2_first') recursedown('./tests/migrations2/test_migrations_2_no_deps') recursedown('./tests/model_enums') recursedown('./tests/model_fields') recursedown('./tests/model_forms') recursedown('./tests/model_formsets') recursedown('./tests/model_formsets_regress') recursedown('./tests/model_indexes') recursedown('./tests/model_inheritance') recursedown('./tests/model_inheritance_regress') recursedown('./tests/model_meta') recursedown('./tests/model_options') recursedown('./tests/model_options/models') recursedown('./tests/model_package') recursedown('./tests/model_package/models') recursedown('./tests/model_regress') recursedown('./tests/model_utils') recursedown('./tests/modeladmin') recursedown('./tests/multiple_database') recursedown('./tests/multiple_database/fixtures') recursedown('./tests/mutually_referential') recursedown('./tests/nested_foreign_keys') recursedown('./tests/no_models') recursedown('./tests/null_fk') recursedown('./tests/null_fk_ordering') recursedown('./tests/null_queries') recursedown('./tests/one_to_one') recursedown('./tests/or_lookups') recursedown('./tests/order_with_respect_to') recursedown('./tests/ordering') recursedown('./tests/pagination') recursedown('./tests/postgres_tests') recursedown('./tests/postgres_tests/array_default_migrations') recursedown('./tests/postgres_tests/array_index_migrations') recursedown('./tests/postgres_tests/migrations') recursedown('./tests/prefetch_related') recursedown('./tests/project_template') recursedown('./tests/properties') recursedown('./tests/proxy_model_inheritance') recursedown('./tests/proxy_model_inheritance/app1') recursedown('./tests/proxy_model_inheritance/app2') recursedown('./tests/proxy_models') recursedown('./tests/proxy_models/fixtures') recursedown('./tests/queries') recursedown('./tests/queryset_pickle') recursedown('./tests/raw_query') recursedown('./tests/redirects_tests') recursedown('./tests/requests_tests') recursedown('./tests/requirements') recursedown('./tests/reserved_names') recursedown('./tests/resolve_url') recursedown('./tests/responses') recursedown('./tests/reverse_lookup') recursedown('./tests/save_delete_hooks') recursedown('./tests/schema') recursedown('./tests/select_for_update') recursedown('./tests/select_related') recursedown('./tests/select_related_onetoone') recursedown('./tests/select_related_regress') recursedown('./tests/serializers') recursedown('./tests/serializers/models') recursedown('./tests/servers') recursedown('./tests/servers/another_app') recursedown('./tests/servers/another_app/static') recursedown('./tests/servers/another_app/static/another_app') recursedown('./tests/servers/fixtures') recursedown('./tests/servers/media') recursedown('./tests/servers/static') recursedown('./tests/sessions_tests') recursedown('./tests/settings_tests') recursedown('./tests/shell') recursedown('./tests/shortcuts') recursedown('./tests/shortcuts/jinja2') recursedown('./tests/shortcuts/jinja2/shortcuts') recursedown('./tests/shortcuts/templates') recursedown('./tests/shortcuts/templates/shortcuts') recursedown('./tests/signals') recursedown('./tests/signed_cookies_tests') recursedown('./tests/signing') recursedown('./tests/sitemaps_tests') recursedown('./tests/sitemaps_tests/templates') recursedown('./tests/sitemaps_tests/urls') recursedown('./tests/sites_framework') recursedown('./tests/sites_framework/migrations') recursedown('./tests/sites_tests') recursedown('./tests/staticfiles_tests') recursedown('./tests/staticfiles_tests/apps') recursedown('./tests/staticfiles_tests/apps/no_label') recursedown('./tests/staticfiles_tests/apps/no_label/static') recursedown('./tests/staticfiles_tests/apps/test') recursedown('./tests/staticfiles_tests/apps/test/otherdir') recursedown('./tests/staticfiles_tests/apps/test/static') recursedown('./tests/staticfiles_tests/apps/test/static/test') recursedown('./tests/staticfiles_tests/apps/test/static/test/vendor') recursedown('./tests/staticfiles_tests/project') recursedown('./tests/staticfiles_tests/project/documents') recursedown('./tests/staticfiles_tests/project/documents/cached') recursedown('./tests/staticfiles_tests/project/documents/cached/css') recursedown('./tests/staticfiles_tests/project/documents/cached/css/fonts') recursedown('./tests/staticfiles_tests/project/documents/cached/css/img') recursedown('./tests/staticfiles_tests/project/documents/cached/img') recursedown('./tests/staticfiles_tests/project/documents/nested') recursedown('./tests/staticfiles_tests/project/documents/nested/css') recursedown('./tests/staticfiles_tests/project/documents/nested/js') recursedown('./tests/staticfiles_tests/project/documents/subdir') recursedown('./tests/staticfiles_tests/project/documents/test') recursedown('./tests/staticfiles_tests/project/faulty') recursedown('./tests/staticfiles_tests/project/loop') recursedown('./tests/staticfiles_tests/project/nonutf8') recursedown('./tests/staticfiles_tests/project/pathlib') recursedown('./tests/staticfiles_tests/project/prefixed') recursedown('./tests/staticfiles_tests/project/site_media') recursedown('./tests/staticfiles_tests/project/site_media/media') recursedown('./tests/staticfiles_tests/project/site_media/static') recursedown('./tests/staticfiles_tests/urls') recursedown('./tests/str') recursedown('./tests/string_lookup') recursedown('./tests/swappable_models') recursedown('./tests/syndication_tests') recursedown('./tests/syndication_tests/templates') recursedown('./tests/syndication_tests/templates/syndication') recursedown('./tests/template_backends') recursedown('./tests/template_backends/apps') recursedown('./tests/template_backends/apps/good') recursedown('./tests/template_backends/apps/good/templatetags') recursedown('./tests/template_backends/apps/good/templatetags/subpackage') recursedown('./tests/template_backends/apps/importerror') recursedown('./tests/template_backends/apps/importerror/templatetags') recursedown('./tests/template_backends/forbidden') recursedown('./tests/template_backends/forbidden/template_backends') recursedown('./tests/template_backends/jinja2') recursedown('./tests/template_backends/jinja2/template_backends') recursedown('./tests/template_backends/template_strings') recursedown('./tests/template_backends/template_strings/template_backends') recursedown('./tests/template_backends/templates') recursedown('./tests/template_backends/templates/template_backends') recursedown('./tests/template_loader') recursedown('./tests/template_loader/template_strings') recursedown('./tests/template_loader/template_strings/template_loader') recursedown('./tests/template_loader/templates') recursedown('./tests/template_loader/templates/template_loader') recursedown('./tests/template_tests') recursedown('./tests/template_tests/eggs') recursedown('./tests/template_tests/filter_tests') recursedown('./tests/template_tests/jinja2') recursedown('./tests/template_tests/jinja2/template_tests') recursedown('./tests/template_tests/other_templates') recursedown('./tests/template_tests/other_templates/priority') recursedown('./tests/template_tests/recursive_templates') recursedown('./tests/template_tests/recursive_templates/fs') recursedown('./tests/template_tests/recursive_templates/fs2') recursedown('./tests/template_tests/recursive_templates/fs3') recursedown('./tests/template_tests/relative_templates') recursedown('./tests/template_tests/relative_templates/dir1') recursedown('./tests/template_tests/relative_templates/dir1/dir2') recursedown('./tests/template_tests/syntax_tests') recursedown('./tests/template_tests/syntax_tests/i18n') recursedown('./tests/template_tests/templates') recursedown('./tests/template_tests/templates/first') recursedown('./tests/template_tests/templates/priority') recursedown('./tests/template_tests/templates/second') recursedown('./tests/template_tests/templates/template_tests') recursedown('./tests/template_tests/templatetags') recursedown('./tests/template_tests/templatetags/subpackage') recursedown('./tests/templates') recursedown('./tests/templates/comments') recursedown('./tests/templates/custom_admin') recursedown('./tests/templates/views') recursedown('./tests/test_client') recursedown('./tests/test_client_regress') recursedown('./tests/test_client_regress/bad_templates') recursedown('./tests/test_client_regress/templates') recursedown('./tests/test_exceptions') recursedown('./tests/test_runner') recursedown('./tests/test_runner_apps') recursedown('./tests/test_runner_apps/buffer') recursedown('./tests/test_runner_apps/databases') recursedown('./tests/test_runner_apps/failures') recursedown('./tests/test_runner_apps/sample') recursedown('./tests/test_runner_apps/sample/tests') recursedown('./tests/test_runner_apps/simple') recursedown('./tests/test_runner_apps/tagged') recursedown('./tests/test_utils') recursedown('./tests/test_utils/fixtures') recursedown('./tests/test_utils/templates') recursedown('./tests/test_utils/templates/template_used') recursedown('./tests/timezones') recursedown('./tests/transaction_hooks') recursedown('./tests/transactions') recursedown('./tests/unmanaged_models') recursedown('./tests/update') recursedown('./tests/update_only_fields') recursedown('./tests/urlpatterns') recursedown('./tests/urlpatterns_reverse') recursedown('./tests/urlpatterns_reverse/translations') recursedown('./tests/urlpatterns_reverse/translations/locale') recursedown('./tests/urlpatterns_reverse/translations/locale/de') recursedown('./tests/urlpatterns_reverse/translations/locale/de/LC_MESSAGES') recursedown('./tests/urlpatterns_reverse/translations/locale/fr') recursedown('./tests/urlpatterns_reverse/translations/locale/fr/LC_MESSAGES') recursedown('./tests/user_commands') recursedown('./tests/user_commands/eggs') recursedown('./tests/user_commands/management') recursedown('./tests/user_commands/management/commands') recursedown('./tests/utils_tests') recursedown('./tests/utils_tests/archives') recursedown('./tests/utils_tests/eggs') recursedown('./tests/utils_tests/files') recursedown('./tests/utils_tests/test_module') recursedown('./tests/utils_tests/test_module/child_module') recursedown('./tests/utils_tests/traversal_archives') recursedown('./tests/validation') recursedown('./tests/validators') recursedown('./tests/version') recursedown('./tests/view_tests') recursedown('./tests/view_tests/app0') recursedown('./tests/view_tests/app0/locale') recursedown('./tests/view_tests/app0/locale/en') recursedown('./tests/view_tests/app0/locale/en/LC_MESSAGES') recursedown('./tests/view_tests/app1') recursedown('./tests/view_tests/app1/locale') recursedown('./tests/view_tests/app1/locale/fr') recursedown('./tests/view_tests/app1/locale/fr/LC_MESSAGES') recursedown('./tests/view_tests/app2') recursedown('./tests/view_tests/app2/locale') recursedown('./tests/view_tests/app2/locale/fr') recursedown('./tests/view_tests/app2/locale/fr/LC_MESSAGES') recursedown('./tests/view_tests/app3') recursedown('./tests/view_tests/app3/locale') recursedown('./tests/view_tests/app3/locale/es_AR') recursedown('./tests/view_tests/app3/locale/es_AR/LC_MESSAGES') recursedown('./tests/view_tests/app4') recursedown('./tests/view_tests/app4/locale') recursedown('./tests/view_tests/app4/locale/es_AR') recursedown('./tests/view_tests/app4/locale/es_AR/LC_MESSAGES') recursedown('./tests/view_tests/app5') recursedown('./tests/view_tests/app5/locale') recursedown('./tests/view_tests/app5/locale/fr') recursedown('./tests/view_tests/app5/locale/fr/LC_MESSAGES') recursedown('./tests/view_tests/custom_locale_path') recursedown('./tests/view_tests/custom_locale_path/es') recursedown('./tests/view_tests/custom_locale_path/es/LC_MESSAGES') recursedown('./tests/view_tests/custom_locale_path/es_MX') recursedown('./tests/view_tests/custom_locale_path/es_MX/LC_MESSAGES') recursedown('./tests/view_tests/locale') recursedown('./tests/view_tests/locale/de') recursedown('./tests/view_tests/locale/de/LC_MESSAGES') recursedown('./tests/view_tests/locale/en_GB') recursedown('./tests/view_tests/locale/en_GB/LC_MESSAGES') recursedown('./tests/view_tests/locale/es') recursedown('./tests/view_tests/locale/es/LC_MESSAGES') recursedown('./tests/view_tests/locale/fr') recursedown('./tests/view_tests/locale/fr/LC_MESSAGES') recursedown('./tests/view_tests/locale/nl') recursedown('./tests/view_tests/locale/nl/LC_MESSAGES') recursedown('./tests/view_tests/locale/pt') recursedown('./tests/view_tests/locale/pt/LC_MESSAGES') recursedown('./tests/view_tests/locale/ru') recursedown('./tests/view_tests/locale/ru/LC_MESSAGES') recursedown('./tests/view_tests/media') recursedown('./tests/view_tests/media/subdir') recursedown('./tests/view_tests/templates') recursedown('./tests/view_tests/templates/debug') recursedown('./tests/view_tests/templatetags') recursedown('./tests/view_tests/tests') recursedown('./tests/wsgi') recursedown('./tests/xor_lookups') + RPM_EC=0 ++ jobs -p + exit 0 + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-ld -Wl,--build-id=sha1' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-5.0.8 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-ld -Wl,--build-id=sha1' + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -s' ./tests/m2o_recursive/tests.py: no change ./tests/mail/__init__.py: no change ./tests/mail/custombackend.py: no change ./tests/mail/test_sendtestemail.py: no change ./tests/mail/tests.py: no change ./tests/managers_regress/__init__.py: no change ./tests/managers_regress/models.py: no change ./tests/managers_regress/tests.py: no change ./tests/many_to_many/__init__.py: no change ./tests/many_to_many/models.py: no change ./tests/many_to_many/tests.py: no change ./tests/many_to_one/__init__.py: no change ./tests/many_to_one/models.py: no change ./tests/many_to_one/tests.py: no change ./tests/many_to_one_null/__init__.py: no change ./tests/many_to_one_null/models.py: no change ./tests/many_to_one_null/tests.py: no change ./tests/max_lengths/__init__.py: no change ./tests/max_lengths/models.py: no change ./tests/max_lengths/tests.py: no change ./tests/messages_tests/__init__.py: no change ./tests/messages_tests/base.py: no change ./tests/messages_tests/models.py: no change ./tests/messages_tests/test_api.py: no change ./tests/messages_tests/test_cookie.py: no change ./tests/messages_tests/test_fallback.py: no change ./tests/messages_tests/test_middleware.py: no change ./tests/messages_tests/test_mixins.py: no change ./tests/messages_tests/test_session.py: no change ./tests/messages_tests/tests.py: no change ./tests/messages_tests/urls.py: no change ./tests/messages_tests/utils.py: no change ./tests/middleware/__init__.py: no change ./tests/middleware/cond_get_urls.py: no change ./tests/middleware/extra_urls.py: no change ./tests/middleware/test_security.py: no change ./tests/middleware/tests.py: no change ./tests/middleware/urls.py: no change ./tests/middleware/views.py: no change ./tests/middleware_exceptions/__init__.py: no change ./tests/middleware_exceptions/middleware.py: no change ./tests/middleware_exceptions/tests.py: no change ./tests/middleware_exceptions/urls.py: no change ./tests/middleware_exceptions/views.py: no change ./tests/migrate_signals/__init__.py: no change ./tests/migrate_signals/models.py: no change ./tests/migrate_signals/tests.py: no change ./tests/migrate_signals/custom_migrations/0001_initial.py: no change ./tests/migrate_signals/custom_migrations/__init__.py: no change ./tests/migration_test_data_persistence/__init__.py: no change ./tests/migration_test_data_persistence/models.py: no change ./tests/migration_test_data_persistence/tests.py: no change ./tests/migration_test_data_persistence/migrations/0001_initial.py: no change ./tests/migration_test_data_persistence/migrations/0002_add_book.py: no change ./tests/migration_test_data_persistence/migrations/__init__.py: no change ./tests/migrations/__init__.py: no change ./tests/migrations/models.py: no change ./tests/migrations/routers.py: no change ./tests/migrations/test_autodetector.py: no change ./tests/migrations/test_base.py: no change ./tests/migrations/test_commands.py: no change ./tests/migrations/test_deprecated_fields.py: no change ./tests/migrations/test_exceptions.py: no change ./tests/migrations/test_executor.py: no change ./tests/migrations/test_graph.py: no change ./tests/migrations/test_loader.py: no change ./tests/migrations/test_multidb.py: no change ./tests/migrations/test_operations.py: no change ./tests/migrations/test_optimizer.py: no change ./tests/migrations/test_questioner.py: no change ./tests/migrations/test_state.py: no change ./tests/migrations/test_writer.py: no change ./tests/migrations/deprecated_field_migrations/0001_initial.py: no change ./tests/migrations/deprecated_field_migrations/0002_remove_ipaddressfield_ip.py: no change ./tests/migrations/deprecated_field_migrations/__init__.py: no change ./tests/migrations/faulty_migrations/__init__.py: no change ./tests/migrations/faulty_migrations/file.py: no change ./tests/migrations/faulty_migrations/namespace/foo/__init__.py: no change ./tests/migrations/migrations_test_apps/__init__.py: no change ./tests/migrations/migrations_test_apps/alter_fk/__init__.py: no change ./tests/migrations/migrations_test_apps/alter_fk/author_app/__init__.py: no change ./tests/migrations/migrations_test_apps/alter_fk/author_app/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/alter_fk/author_app/migrations/0002_alter_id.py: no change ./tests/migrations/migrations_test_apps/alter_fk/author_app/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/alter_fk/book_app/__init__.py: no change ./tests/migrations/migrations_test_apps/alter_fk/book_app/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/alter_fk/book_app/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies/__init__.py: no change ./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies/migrations/0002_conflicting_second.py: no change ./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies/migrations/0002_second.py: no change ./tests/migrations/migrations_test_apps/conflicting_app_with_dependencies/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/__init__.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/models.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/migrations/0002_a2.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/migrations/0003_a3.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/migrations/0004_a4.py: no change ./tests/migrations/migrations_test_apps/lookuperror_a/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/lookuperror_b/__init__.py: no change ./tests/migrations/migrations_test_apps/lookuperror_b/models.py: no change ./tests/migrations/migrations_test_apps/lookuperror_b/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/lookuperror_b/migrations/0002_b2.py: no change ./tests/migrations/migrations_test_apps/lookuperror_b/migrations/0003_b3.py: no change ./tests/migrations/migrations_test_apps/lookuperror_b/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/lookuperror_c/__init__.py: no change ./tests/migrations/migrations_test_apps/lookuperror_c/models.py: no change ./tests/migrations/migrations_test_apps/lookuperror_c/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/lookuperror_c/migrations/0002_c2.py: no change ./tests/migrations/migrations_test_apps/lookuperror_c/migrations/0003_c3.py: no change ./tests/migrations/migrations_test_apps/lookuperror_c/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/migrated_app/__init__.py: no change ./tests/migrations/migrations_test_apps/migrated_app/models.py: no change ./tests/migrations/migrations_test_apps/migrated_app/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/migrated_app/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/migrated_unapplied_app/__init__.py: no change ./tests/migrations/migrations_test_apps/migrated_unapplied_app/models.py: no change ./tests/migrations/migrations_test_apps/migrated_unapplied_app/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/migrated_unapplied_app/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/mutate_state_a/__init__.py: no change ./tests/migrations/migrations_test_apps/mutate_state_a/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/mutate_state_a/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/mutate_state_b/__init__.py: no change ./tests/migrations/migrations_test_apps/mutate_state_b/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/mutate_state_b/migrations/0002_add_field.py: no change ./tests/migrations/migrations_test_apps/mutate_state_b/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/normal/__init__.py: no change ./tests/migrations/migrations_test_apps/unmigrated_app/__init__.py: no change ./tests/migrations/migrations_test_apps/unmigrated_app/models.py: no change ./tests/migrations/migrations_test_apps/unmigrated_app_simple/__init__.py: no change ./tests/migrations/migrations_test_apps/unmigrated_app_simple/models.py: no change ./tests/migrations/migrations_test_apps/unmigrated_app_syncdb/__init__.py: no change ./tests/migrations/migrations_test_apps/unmigrated_app_syncdb/models.py: no change ./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/__init__.py: no change ./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/models.py: no change ./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/migrations/0001_initial.py: no change ./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/migrations/0002_conflicting_second.py: no change ./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/migrations/0002_second.py: no change ./tests/migrations/migrations_test_apps/unspecified_app_with_conflict/migrations/__init__.py: no change ./tests/migrations/migrations_test_apps/with_package_model/__init__.py: no change ./tests/migrations/migrations_test_apps/with_package_model/models/__init__.py: no change ./tests/migrations/migrations_test_apps/without_init_file/__init__.py: no change ./tests/migrations/related_models_app/__init__.py: no change ./tests/migrations/test_add_many_to_many_field_initial/0001_initial.py: no change ./tests/migrations/test_add_many_to_many_field_initial/0002_initial.py: no change ./tests/migrations/test_add_many_to_many_field_initial/__init__.py: no change ./tests/migrations/test_auto_now_add/0001_initial.py: no change ./tests/migrations/test_auto_now_add/__init__.py: no change ./tests/migrations/test_fake_initial_case_insensitive/fake_initial/0001_initial.py: no change ./tests/migrations/test_fake_initial_case_insensitive/fake_initial/__init__.py: no change ./tests/migrations/test_fake_initial_case_insensitive/initial/0001_initial.py: no change ./tests/migrations/test_fake_initial_case_insensitive/initial/__init__.py: no change ./tests/migrations/test_migrations/0001_initial.py: no change ./tests/migrations/test_migrations/0002_second.py: no change ./tests/migrations/test_migrations/__init__.py: no change ./tests/migrations/test_migrations_atomic_operation/0001_initial.py: no change ./tests/migrations/test_migrations_atomic_operation/__init__.py: no change ./tests/migrations/test_migrations_backwards_deps_1/0001_initial.py: no change ./tests/migrations/test_migrations_backwards_deps_1/0002_second.py: no change ./tests/migrations/test_migrations_bad_pyc/__init__.py: no change ./tests/migrations/test_migrations_clashing_prefix/__init__.py: no change ./tests/migrations/test_migrations_clashing_prefix/a.py: no change ./tests/migrations/test_migrations_clashing_prefix/ab.py: no change ./tests/migrations/test_migrations_conflict/0001_initial.py: no change ./tests/migrations/test_migrations_conflict/0002_conflicting_second.py: no change ./tests/migrations/test_migrations_conflict/0002_second.py: no change ./tests/migrations/test_migrations_conflict/__init__.py: no change ./tests/migrations/test_migrations_conflict_long_name/0001_initial.py: no change ./tests/migrations/test_migrations_conflict_long_name/0002_conflicting_second_migration_with_long_name.py: no change ./tests/migrations/test_migrations_conflict_long_name/0002_second.py: no change ./tests/migrations/test_migrations_conflict_long_name/__init__.py: no change ./tests/migrations/test_migrations_custom_user/0001_initial.py: no change ./tests/migrations/test_migrations_custom_user/__init__.py: no change ./tests/migrations/test_migrations_empty/__init__.py: no change ./tests/migrations/test_migrations_fake_split_initial/0001_initial.py: no change ./tests/migrations/test_migrations_fake_split_initial/0002_second.py: no change ./tests/migrations/test_migrations_fake_split_initial/__init__.py: no change ./tests/migrations/test_migrations_first/__init__.py: no change ./tests/migrations/test_migrations_first/second.py: no change ./tests/migrations/test_migrations_first/thefirst.py: no change ./tests/migrations/test_migrations_initial_false/0001_not_initial.py: no change ./tests/migrations/test_migrations_initial_false/__init__.py: no change ./tests/migrations/test_migrations_manual_porting/0001_initial.py: no change ./tests/migrations/test_migrations_manual_porting/0002_second.py: no change ./tests/migrations/test_migrations_manual_porting/0003_third.py: no change ./tests/migrations/test_migrations_manual_porting/0004_fourth.py: no change ./tests/migrations/test_migrations_manual_porting/__init__.py: no change ./tests/migrations/test_migrations_namespace_package/0001_initial.py: no change ./tests/migrations/test_migrations_no_ancestor/0001_initial.py: no change ./tests/migrations/test_migrations_no_ancestor/0002_conflicting_second.py: no change ./tests/migrations/test_migrations_no_ancestor/0002_second.py: no change ./tests/migrations/test_migrations_no_ancestor/__init__.py: no change ./tests/migrations/test_migrations_no_changes/0001_initial.py: no change ./tests/migrations/test_migrations_no_changes/0002_second.py: no change ./tests/migrations/test_migrations_no_changes/0003_third.py: no change ./tests/migrations/test_migrations_no_changes/__init__.py: no change ./tests/migrations/test_migrations_no_default/0001_initial.py: no change ./tests/migrations/test_migrations_no_default/__init__.py: no change ./tests/migrations/test_migrations_no_operations/0001_initial.py: no change ./tests/migrations/test_migrations_no_operations/__init__.py: no change ./tests/migrations/test_migrations_non_atomic/0001_initial.py: no change ./tests/migrations/test_migrations_non_atomic/__init__.py: no change ./tests/migrations/test_migrations_noop/0001_initial.py: no change ./tests/migrations/test_migrations_noop/__init__.py: no change ./tests/migrations/test_migrations_order/0001.py: no change ./tests/migrations/test_migrations_order/__init__.py: no change ./tests/migrations/test_migrations_plan/0001_initial.py: no change ./tests/migrations/test_migrations_plan/0002_second.py: no change ./tests/migrations/test_migrations_plan/0003_third.py: no change ./tests/migrations/test_migrations_plan/0004_fourth.py: no change ./tests/migrations/test_migrations_plan/0005_fifth.py: no change ./tests/migrations/test_migrations_plan/__init__.py: no change ./tests/migrations/test_migrations_private/.util.py: no change ./tests/migrations/test_migrations_private/0001_initial.py: no change ./tests/migrations/test_migrations_private/__init__.py: no change ./tests/migrations/test_migrations_private/_util.py: no change ./tests/migrations/test_migrations_private/~util.py: no change ./tests/migrations/test_migrations_run_before/0001_initial.py: no change ./tests/migrations/test_migrations_run_before/0002_second.py: no change ./tests/migrations/test_migrations_run_before/0003_third.py: no change ./tests/migrations/test_migrations_run_before/__init__.py: no change ./tests/migrations/test_migrations_squashed/0001_initial.py: no change ./tests/migrations/test_migrations_squashed/0001_squashed_0002.py: no change ./tests/migrations/test_migrations_squashed/0002_second.py: no change ./tests/migrations/test_migrations_squashed/__init__.py: no change ./tests/migrations/test_migrations_squashed_complex/1_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/2_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/3_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/3_squashed_5.py: no change ./tests/migrations/test_migrations_squashed_complex/4_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/5_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/6_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/7_auto.py: no change ./tests/migrations/test_migrations_squashed_complex/__init__.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/__init__.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app1/1_auto.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app1/2_auto.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app1/2_squashed_3.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app1/3_auto.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app1/4_auto.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app1/__init__.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app2/1_auto.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app2/1_squashed_2.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app2/2_auto.py: no change ./tests/migrations/test_migrations_squashed_complex_multi_apps/app2/__init__.py: no change ./tests/migrations/test_migrations_squashed_erroneous/1_auto.py: no change ./tests/migrations/test_migrations_squashed_erroneous/2_auto.py: no change ./tests/migrations/test_migrations_squashed_erroneous/3_squashed_5.py: no change ./tests/migrations/test_migrations_squashed_erroneous/6_auto.py: no change ./tests/migrations/test_migrations_squashed_erroneous/7_auto.py: no change ./tests/migrations/test_migrations_squashed_erroneous/__init__.py: no change ./tests/migrations/test_migrations_squashed_extra/0001_initial.py: no change ./tests/migrations/test_migrations_squashed_extra/0001_squashed_0002.py: no change ./tests/migrations/test_migrations_squashed_extra/0002_second.py: no change ./tests/migrations/test_migrations_squashed_extra/0003_third.py: no change ./tests/migrations/test_migrations_squashed_extra/__init__.py: no change ./tests/migrations/test_migrations_squashed_no_replaces/0001_squashed_0002.py: no change ./tests/migrations/test_migrations_squashed_no_replaces/__init__.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/__init__.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app1/1_auto.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app1/2_auto.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app1/2_squashed_3.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app1/3_auto.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app1/4_auto.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app1/__init__.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app2/1_auto.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app2/1_squashed_2.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app2/2_auto.py: no change ./tests/migrations/test_migrations_squashed_ref_squashed/app2/__init__.py: no change ./tests/migrations/test_migrations_unmigdep/0001_initial.py: no change ./tests/migrations/test_migrations_unmigdep/__init__.py: no change ./tests/migrations2/__init__.py: no change ./tests/migrations2/models.py: no change ./tests/migrations2/test_migrations_2/0001_initial.py: no change ./tests/migrations2/test_migrations_2/__init__.py: no change ./tests/migrations2/test_migrations_2_first/0001_initial.py: no change ./tests/migrations2/test_migrations_2_first/0002_second.py: no change ./tests/migrations2/test_migrations_2_first/__init__.py: no change ./tests/migrations2/test_migrations_2_no_deps/0001_initial.py: no change ./tests/migrations2/test_migrations_2_no_deps/__init__.py: no change ./tests/model_enums/__init__.py: no change ./tests/model_enums/tests.py: no change ./tests/model_fields/__init__.py: no change ./tests/model_fields/models.py: no change ./tests/model_fields/test_autofield.py: no change ./tests/model_fields/test_binaryfield.py: no change ./tests/model_fields/test_booleanfield.py: no change ./tests/model_fields/test_charfield.py: no change ./tests/model_fields/test_datetimefield.py: no change ./tests/model_fields/test_decimalfield.py: no change ./tests/model_fields/test_durationfield.py: no change ./tests/model_fields/test_field_flags.py: no change ./tests/model_fields/test_filefield.py: no change ./tests/model_fields/test_filepathfield.py: no change ./tests/model_fields/test_floatfield.py: no change ./tests/model_fields/test_foreignkey.py: no change ./tests/model_fields/test_generatedfield.py: no change ./tests/model_fields/test_genericipaddressfield.py: no change ./tests/model_fields/test_imagefield.py: no change ./tests/model_fields/test_integerfield.py: no change ./tests/model_fields/test_jsonfield.py: no change ./tests/model_fields/test_manytomanyfield.py: no change ./tests/model_fields/test_promises.py: no change ./tests/model_fields/test_slugfield.py: no change ./tests/model_fields/test_textfield.py: no change ./tests/model_fields/test_uuid.py: no change ./tests/model_fields/tests.py: no change ./tests/model_forms/__init__.py: no change ./tests/model_forms/models.py: no change ./tests/model_forms/test_modelchoicefield.py: no change ./tests/model_forms/test_uuid.py: no change ./tests/model_forms/tests.py: no change ./tests/model_formsets/__init__.py: no change ./tests/model_formsets/models.py: no change ./tests/model_formsets/test_uuid.py: no change ./tests/model_formsets/tests.py: no change ./tests/model_formsets_regress/__init__.py: no change ./tests/model_formsets_regress/models.py: no change ./tests/model_formsets_regress/tests.py: no change ./tests/model_indexes/__init__.py: no change ./tests/model_indexes/models.py: no change ./tests/model_indexes/tests.py: no change ./tests/model_inheritance/__init__.py: no change ./tests/model_inheritance/models.py: no change ./tests/model_inheritance/test_abstract_inheritance.py: no change ./tests/model_inheritance/tests.py: no change ./tests/model_inheritance_regress/__init__.py: no change ./tests/model_inheritance_regress/models.py: no change ./tests/model_inheritance_regress/tests.py: no change ./tests/model_meta/__init__.py: no change ./tests/model_meta/models.py: no change ./tests/model_meta/results.py: no change ./tests/model_meta/tests.py: no change ./tests/model_options/__init__.py: no change ./tests/model_options/apps.py: no change ./tests/model_options/test_default_pk.py: no change ./tests/model_options/test_default_related_name.py: no change ./tests/model_options/test_tablespaces.py: no change ./tests/model_options/models/__init__.py: no change ./tests/model_options/models/default_related_name.py: no change ./tests/model_options/models/tablespaces.py: no change ./tests/model_package/__init__.py: no change ./tests/model_package/tests.py: no change ./tests/model_package/models/__init__.py: no change ./tests/model_package/models/article.py: no change ./tests/model_package/models/publication.py: no change ./tests/model_regress/__init__.py: no change ./tests/model_regress/models.py: no change ./tests/model_regress/test_pickle.py: no change ./tests/model_regress/test_state.py: no change ./tests/model_regress/tests.py: no change ./tests/model_utils/__init__.py: no change ./tests/model_utils/tests.py: no change ./tests/modeladmin/__init__.py: no change ./tests/modeladmin/models.py: no change ./tests/modeladmin/test_actions.py: no change ./tests/modeladmin/test_checks.py: no change ./tests/modeladmin/tests.py: no change ./tests/multiple_database/__init__.py: no change ./tests/multiple_database/models.py: no change ./tests/multiple_database/routers.py: no change ./tests/multiple_database/tests.py: no change ./tests/mutually_referential/__init__.py: no change ./tests/mutually_referential/models.py: no change ./tests/mutually_referential/tests.py: no change ./tests/nested_foreign_keys/__init__.py: no change ./tests/nested_foreign_keys/models.py: no change ./tests/nested_foreign_keys/tests.py: no change ./tests/no_models/__init__.py: no change ./tests/no_models/tests.py: no change ./tests/null_fk/__init__.py: no change ./tests/null_fk/models.py: no change ./tests/null_fk/tests.py: no change ./tests/null_fk_ordering/__init__.py: no change ./tests/null_fk_ordering/models.py: no change ./tests/null_fk_ordering/tests.py: no change ./tests/null_queries/__init__.py: no change ./tests/null_queries/models.py: no change ./tests/null_queries/tests.py: no change ./tests/one_to_one/__init__.py: no change ./tests/one_to_one/models.py: no change ./tests/one_to_one/tests.py: no change ./tests/or_lookups/__init__.py: no change ./tests/or_lookups/models.py: no change ./tests/or_lookups/tests.py: no change ./tests/order_with_respect_to/__init__.py: no change ./tests/order_with_respect_to/base_tests.py: no change ./tests/order_with_respect_to/models.py: no change ./tests/order_with_respect_to/tests.py: no change ./tests/ordering/__init__.py: no change ./tests/ordering/models.py: no change ./tests/ordering/tests.py: no change ./tests/pagination/__init__.py: no change ./tests/pagination/custom.py: no change ./tests/pagination/models.py: no change ./tests/pagination/tests.py: no change ./tests/postgres_tests/__init__.py: no change ./tests/postgres_tests/fields.py: no change ./tests/postgres_tests/integration_settings.py: no change ./tests/postgres_tests/models.py: no change ./tests/postgres_tests/test_aggregates.py: no change ./tests/postgres_tests/test_apps.py: no change ./tests/postgres_tests/test_array.py: no change ./tests/postgres_tests/test_bulk_update.py: no change ./tests/postgres_tests/test_citext.py: no change ./tests/postgres_tests/test_constraints.py: no change ./tests/postgres_tests/test_functions.py: no change ./tests/postgres_tests/test_hstore.py: no change ./tests/postgres_tests/test_indexes.py: no change ./tests/postgres_tests/test_integration.py: no change ./tests/postgres_tests/test_introspection.py: no change ./tests/postgres_tests/test_operations.py: no change ./tests/postgres_tests/test_ranges.py: no change ./tests/postgres_tests/test_search.py: no change ./tests/postgres_tests/test_signals.py: no change ./tests/postgres_tests/test_trigram.py: no change ./tests/postgres_tests/test_unaccent.py: no change ./tests/postgres_tests/array_default_migrations/0001_initial.py: no change ./tests/postgres_tests/array_default_migrations/0002_integerarraymodel_field_2.py: no change ./tests/postgres_tests/array_default_migrations/__init__.py: no change ./tests/postgres_tests/array_index_migrations/0001_initial.py: no change ./tests/postgres_tests/array_index_migrations/__init__.py: no change ./tests/postgres_tests/migrations/0001_setup_extensions.py: no change ./tests/postgres_tests/migrations/0002_create_test_models.py: no change ./tests/postgres_tests/migrations/__init__.py: no change ./tests/prefetch_related/__init__.py: no change ./tests/prefetch_related/models.py: no change ./tests/prefetch_related/test_prefetch_related_objects.py: no change ./tests/prefetch_related/test_uuid.py: no change ./tests/prefetch_related/tests.py: no change ./tests/project_template/__init__.py: no change ./tests/project_template/test_settings.py: no change ./tests/project_template/urls.py: no change ./tests/project_template/views.py: no change ./tests/properties/__init__.py: no change ./tests/properties/models.py: no change ./tests/properties/tests.py: no change ./tests/proxy_model_inheritance/__init__.py: no change ./tests/proxy_model_inheritance/models.py: no change ./tests/proxy_model_inheritance/tests.py: no change ./tests/proxy_model_inheritance/app1/__init__.py: no change ./tests/proxy_model_inheritance/app1/models.py: no change ./tests/proxy_model_inheritance/app2/__init__.py: no change ./tests/proxy_model_inheritance/app2/models.py: no change ./tests/proxy_models/__init__.py: no change ./tests/proxy_models/admin.py: no change ./tests/proxy_models/models.py: no change ./tests/proxy_models/tests.py: no change ./tests/proxy_models/urls.py: no change ./tests/queries/__init__.py: no change ./tests/queries/models.py: no change ./tests/queries/test_bulk_update.py: no change ./tests/queries/test_contains.py: no change ./tests/queries/test_db_returning.py: no change ./tests/queries/test_explain.py: no change ./tests/queries/test_iterator.py: no change ./tests/queries/test_q.py: no change ./tests/queries/test_qs_combinators.py: no change ./tests/queries/test_query.py: no change ./tests/queries/test_sqlcompiler.py: no change ./tests/queries/tests.py: no change ./tests/queryset_pickle/__init__.py: no change ./tests/queryset_pickle/models.py: no change ./tests/queryset_pickle/tests.py: no change ./tests/raw_query/__init__.py: no change ./tests/raw_query/models.py: no change ./tests/raw_query/tests.py: no change ./tests/redirects_tests/__init__.py: no change ./tests/redirects_tests/tests.py: no change ./tests/redirects_tests/urls.py: no change ./tests/requests_tests/__init__.py: no change ./tests/requests_tests/test_accept_header.py: no change ./tests/requests_tests/test_data_upload_settings.py: no change ./tests/requests_tests/tests.py: no change ./tests/reserved_names/__init__.py: no change ./tests/reserved_names/models.py: no change ./tests/reserved_names/tests.py: no change ./tests/resolve_url/__init__.py: no change ./tests/resolve_url/models.py: no change ./tests/resolve_url/tests.py: no change ./tests/resolve_url/urls.py: no change ./tests/responses/__init__.py: no change ./tests/responses/test_cookie.py: no change ./tests/responses/test_fileresponse.py: no change ./tests/responses/tests.py: no change ./tests/reverse_lookup/__init__.py: no change ./tests/reverse_lookup/models.py: no change ./tests/reverse_lookup/tests.py: no change ./tests/save_delete_hooks/__init__.py: no change ./tests/save_delete_hooks/models.py: no change ./tests/save_delete_hooks/tests.py: no change ./tests/schema/__init__.py: no change ./tests/schema/fields.py: no change ./tests/schema/models.py: no change ./tests/schema/test_logging.py: no change ./tests/schema/tests.py: no change ./tests/select_for_update/__init__.py: no change ./tests/select_for_update/models.py: no change ./tests/select_for_update/tests.py: no change ./tests/select_related/__init__.py: no change ./tests/select_related/models.py: no change ./tests/select_related/tests.py: no change ./tests/select_related_onetoone/__init__.py: no change ./tests/select_related_onetoone/models.py: no change ./tests/select_related_onetoone/tests.py: no change ./tests/select_related_regress/__init__.py: no change ./tests/select_related_regress/models.py: no change ./tests/select_related_regress/tests.py: no change ./tests/serializers/__init__.py: no change ./tests/serializers/test_data.py: no change ./tests/serializers/test_deserializedobject.py: no change ./tests/serializers/test_json.py: no change ./tests/serializers/test_jsonl.py: no change ./tests/serializers/test_natural.py: no change ./tests/serializers/test_xml.py: no change ./tests/serializers/test_yaml.py: no change ./tests/serializers/tests.py: no change ./tests/serializers/models/__init__.py: no change ./tests/serializers/models/base.py: no change ./tests/serializers/models/data.py: no change ./tests/serializers/models/multi_table.py: no change ./tests/serializers/models/natural.py: no change ./tests/servers/__init__.py: no change ./tests/servers/models.py: no change ./tests/servers/test_basehttp.py: no change ./tests/servers/test_liveserverthread.py: no change ./tests/servers/tests.py: no change ./tests/servers/urls.py: no change ./tests/servers/views.py: no change ./tests/servers/another_app/__init__.py: no change ./tests/sessions_tests/__init__.py: no change ./tests/sessions_tests/models.py: no change ./tests/sessions_tests/no_clear_expired.py: no change ./tests/sessions_tests/tests.py: no change ./tests/settings_tests/__init__.py: no change ./tests/settings_tests/tests.py: no change ./tests/shell/__init__.py: no change ./tests/shell/tests.py: no change ./tests/shortcuts/__init__.py: no change ./tests/shortcuts/tests.py: no change ./tests/shortcuts/urls.py: no change ./tests/shortcuts/views.py: no change ./tests/signals/__init__.py: no change ./tests/signals/models.py: no change ./tests/signals/tests.py: no change ./tests/signed_cookies_tests/__init__.py: no change ./tests/signed_cookies_tests/tests.py: no change ./tests/signing/__init__.py: no change ./tests/signing/tests.py: no change ./tests/sitemaps_tests/__init__.py: no change ./tests/sitemaps_tests/base.py: no change ./tests/sitemaps_tests/models.py: no change ./tests/sitemaps_tests/test_generic.py: no change ./tests/sitemaps_tests/test_http.py: no change ./tests/sitemaps_tests/test_https.py: no change ./tests/sitemaps_tests/urls/__init__.py: no change ./tests/sitemaps_tests/urls/http.py: no change ./tests/sitemaps_tests/urls/https.py: no change ./tests/sites_framework/__init__.py: no change ./tests/sites_framework/models.py: no change ./tests/sites_framework/tests.py: no change ./tests/sites_framework/migrations/0001_initial.py: no change ./tests/sites_framework/migrations/__init__.py: no change ./tests/sites_tests/__init__.py: no change ./tests/sites_tests/tests.py: no change ./tests/staticfiles_tests/__init__.py: no change ./tests/staticfiles_tests/cases.py: no change ./tests/staticfiles_tests/settings.py: no change ./tests/staticfiles_tests/storage.py: no change ./tests/staticfiles_tests/test_checks.py: no change ./tests/staticfiles_tests/test_finders.py: no change ./tests/staticfiles_tests/test_forms.py: no change ./tests/staticfiles_tests/test_handlers.py: no change ./tests/staticfiles_tests/test_liveserver.py: no change ./tests/staticfiles_tests/test_management.py: no change ./tests/staticfiles_tests/test_storage.py: no change ./tests/staticfiles_tests/test_templatetags.py: no change ./tests/staticfiles_tests/test_utils.py: no change ./tests/staticfiles_tests/test_views.py: no change ./tests/staticfiles_tests/apps/__init__.py: no change ./tests/staticfiles_tests/apps/staticfiles_config.py: no change ./tests/staticfiles_tests/apps/no_label/__init__.py: no change ./tests/staticfiles_tests/apps/test/__init__.py: no change ./tests/staticfiles_tests/urls/__init__.py: no change ./tests/staticfiles_tests/urls/default.py: no change ./tests/staticfiles_tests/urls/helper.py: no change ./tests/str/__init__.py: no change ./tests/str/models.py: no change ./tests/str/tests.py: no change ./tests/string_lookup/__init__.py: no change ./tests/string_lookup/models.py: no change ./tests/string_lookup/tests.py: no change ./tests/swappable_models/__init__.py: no change ./tests/swappable_models/models.py: no change ./tests/swappable_models/tests.py: no change ./tests/syndication_tests/__init__.py: no change ./tests/syndication_tests/feeds.py: no change ./tests/syndication_tests/models.py: no change ./tests/syndication_tests/tests.py: no change ./tests/syndication_tests/urls.py: no change ./tests/template_backends/__init__.py: no change ./tests/template_backends/test_django.py: no change ./tests/template_backends/test_dummy.py: no change ./tests/template_backends/test_jinja2.py: no change ./tests/template_backends/test_utils.py: no change ./tests/template_backends/apps/__init__.py: no change ./tests/template_backends/apps/good/__init__.py: no change ./tests/template_backends/apps/good/templatetags/__init__.py: no change ./tests/template_backends/apps/good/templatetags/empty.py: no change ./tests/template_backends/apps/good/templatetags/good_tags.py: no change ./tests/template_backends/apps/good/templatetags/override.py: no change ./tests/template_backends/apps/good/templatetags/subpackage/__init__.py: no change ./tests/template_backends/apps/good/templatetags/subpackage/tags.py: no change ./tests/template_backends/apps/importerror/__init__.py: no change ./tests/template_backends/apps/importerror/templatetags/__init__.py: no change ./tests/template_backends/apps/importerror/templatetags/broken_tags.py: no change ./tests/template_loader/__init__.py: no change ./tests/template_loader/tests.py: no change ./tests/template_tests/__init__.py: no change ./tests/template_tests/alternate_urls.py: no change ./tests/template_tests/annotated_tag_function.py: no change ./tests/template_tests/broken_tag.py: no change ./tests/template_tests/test_autoreloader.py: no change ./tests/template_tests/test_base.py: no change ./tests/template_tests/test_callables.py: no change ./tests/template_tests/test_context.py: no change ./tests/template_tests/test_custom.py: no change ./tests/template_tests/test_engine.py: no change ./tests/template_tests/test_extends.py: no change ./tests/template_tests/test_extends_relative.py: no change ./tests/template_tests/test_library.py: no change ./tests/template_tests/test_loaders.py: no change ./tests/template_tests/test_logging.py: no change ./tests/template_tests/test_nodelist.py: no change ./tests/template_tests/test_origin.py: no change ./tests/template_tests/test_parser.py: no change ./tests/template_tests/test_response.py: no change ./tests/template_tests/test_smartif.py: no change ./tests/template_tests/tests.py: no change ./tests/template_tests/urls.py: no change ./tests/template_tests/utils.py: no change ./tests/template_tests/views.py: no change ./tests/template_tests/filter_tests/__init__.py: no change ./tests/template_tests/filter_tests/test_add.py: no change ./tests/template_tests/filter_tests/test_addslashes.py: no change ./tests/template_tests/filter_tests/test_autoescape.py: no change ./tests/template_tests/filter_tests/test_capfirst.py: no change ./tests/template_tests/filter_tests/test_center.py: no change ./tests/template_tests/filter_tests/test_chaining.py: no change ./tests/template_tests/filter_tests/test_cut.py: no change ./tests/template_tests/filter_tests/test_date.py: no change ./tests/template_tests/filter_tests/test_default.py: no change ./tests/template_tests/filter_tests/test_default_if_none.py: no change ./tests/template_tests/filter_tests/test_dictsort.py: no change ./tests/template_tests/filter_tests/test_dictsortreversed.py: no change ./tests/template_tests/filter_tests/test_divisibleby.py: no change ./tests/template_tests/filter_tests/test_escape.py: no change ./tests/template_tests/filter_tests/test_escapejs.py: no change ./tests/template_tests/filter_tests/test_escapeseq.py: no change ./tests/template_tests/filter_tests/test_filesizeformat.py: no change ./tests/template_tests/filter_tests/test_first.py: no change ./tests/template_tests/filter_tests/test_floatformat.py: no change ./tests/template_tests/filter_tests/test_force_escape.py: no change ./tests/template_tests/filter_tests/test_get_digit.py: no change ./tests/template_tests/filter_tests/test_iriencode.py: no change ./tests/template_tests/filter_tests/test_join.py: no change ./tests/template_tests/filter_tests/test_json_script.py: no change ./tests/template_tests/filter_tests/test_last.py: no change ./tests/template_tests/filter_tests/test_length.py: no change ./tests/template_tests/filter_tests/test_length_is.py: no change ./tests/template_tests/filter_tests/test_linebreaks.py: no change ./tests/template_tests/filter_tests/test_linebreaksbr.py: no change ./tests/template_tests/filter_tests/test_linenumbers.py: no change ./tests/template_tests/filter_tests/test_ljust.py: no change ./tests/template_tests/filter_tests/test_lower.py: no change ./tests/template_tests/filter_tests/test_make_list.py: no change ./tests/template_tests/filter_tests/test_phone2numeric.py: no change ./tests/template_tests/filter_tests/test_pluralize.py: no change ./tests/template_tests/filter_tests/test_random.py: no change ./tests/template_tests/filter_tests/test_rjust.py: no change ./tests/template_tests/filter_tests/test_safe.py: no change ./tests/template_tests/filter_tests/test_safeseq.py: no change ./tests/template_tests/filter_tests/test_slice.py: no change ./tests/template_tests/filter_tests/test_slugify.py: no change ./tests/template_tests/filter_tests/test_stringformat.py: no change ./tests/template_tests/filter_tests/test_striptags.py: no change ./tests/template_tests/filter_tests/test_time.py: no change ./tests/template_tests/filter_tests/test_timesince.py: no change ./tests/template_tests/filter_tests/test_timeuntil.py: no change ./tests/template_tests/filter_tests/test_title.py: no change ./tests/template_tests/filter_tests/test_truncatechars.py: no change ./tests/template_tests/filter_tests/test_truncatechars_html.py: no change ./tests/template_tests/filter_tests/test_truncatewords.py: no change ./tests/template_tests/filter_tests/test_truncatewords_html.py: no change ./tests/template_tests/filter_tests/test_unordered_list.py: no change ./tests/template_tests/filter_tests/test_upper.py: no change ./tests/template_tests/filter_tests/test_urlencode.py: no change ./tests/template_tests/filter_tests/test_urlize.py: no change ./tests/template_tests/filter_tests/test_urlizetrunc.py: no change ./tests/template_tests/filter_tests/test_wordcount.py: no change ./tests/template_tests/filter_tests/test_wordwrap.py: no change ./tests/template_tests/filter_tests/test_yesno.py: no change ./tests/template_tests/filter_tests/timezone_utils.py: no change ./tests/template_tests/syntax_tests/__init__.py: no change ./tests/template_tests/syntax_tests/test_autoescape.py: no change ./tests/template_tests/syntax_tests/test_basic.py: no change ./tests/template_tests/syntax_tests/test_builtins.py: no change ./tests/template_tests/syntax_tests/test_cache.py: no change ./tests/template_tests/syntax_tests/test_comment.py: no change ./tests/template_tests/syntax_tests/test_cycle.py: no change ./tests/template_tests/syntax_tests/test_debug.py: no change ./tests/template_tests/syntax_tests/test_exceptions.py: no change ./tests/template_tests/syntax_tests/test_extends.py: no change ./tests/template_tests/syntax_tests/test_filter_syntax.py: no change ./tests/template_tests/syntax_tests/test_filter_tag.py: no change ./tests/template_tests/syntax_tests/test_firstof.py: no change ./tests/template_tests/syntax_tests/test_for.py: no change ./tests/template_tests/syntax_tests/test_if.py: no change ./tests/template_tests/syntax_tests/test_if_changed.py: no change ./tests/template_tests/syntax_tests/test_include.py: no change ./tests/template_tests/syntax_tests/test_invalid_string.py: no change ./tests/template_tests/syntax_tests/test_list_index.py: no change ./tests/template_tests/syntax_tests/test_load.py: no change ./tests/template_tests/syntax_tests/test_lorem.py: no change ./tests/template_tests/syntax_tests/test_multiline.py: no change ./tests/template_tests/syntax_tests/test_named_endblock.py: no change ./tests/template_tests/syntax_tests/test_now.py: no change ./tests/template_tests/syntax_tests/test_numpy.py: no change ./tests/template_tests/syntax_tests/test_regroup.py: no change ./tests/template_tests/syntax_tests/test_resetcycle.py: no change ./tests/template_tests/syntax_tests/test_setup.py: no change ./tests/template_tests/syntax_tests/test_simple_tag.py: no change ./tests/template_tests/syntax_tests/test_spaceless.py: no change ./tests/template_tests/syntax_tests/test_static.py: no change ./tests/template_tests/syntax_tests/test_template_tag.py: no change ./tests/template_tests/syntax_tests/test_url.py: no change ./tests/template_tests/syntax_tests/test_verbatim.py: no change ./tests/template_tests/syntax_tests/test_width_ratio.py: no change ./tests/template_tests/syntax_tests/test_with.py: no change ./tests/template_tests/syntax_tests/i18n/__init__.py: no change ./tests/template_tests/syntax_tests/i18n/base.py: no change ./tests/template_tests/syntax_tests/i18n/test_blocktranslate.py: no change ./tests/template_tests/syntax_tests/i18n/test_filters.py: no change ./tests/template_tests/syntax_tests/i18n/test_get_available_languages.py: no change ./tests/template_tests/syntax_tests/i18n/test_get_current_language.py: no change ./tests/template_tests/syntax_tests/i18n/test_get_current_language_bidi.py: no change ./tests/template_tests/syntax_tests/i18n/test_get_language_info.py: no change ./tests/template_tests/syntax_tests/i18n/test_get_language_info_list.py: no change ./tests/template_tests/syntax_tests/i18n/test_language.py: no change ./tests/template_tests/syntax_tests/i18n/test_translate.py: no change ./tests/template_tests/syntax_tests/i18n/test_underscore_syntax.py: no change ./tests/template_tests/templatetags/__init__.py: no change ./tests/template_tests/templatetags/bad_tag.py: no change ./tests/template_tests/templatetags/custom.py: no change ./tests/template_tests/templatetags/inclusion.py: no change ./tests/template_tests/templatetags/tag_27584.py: no change ./tests/template_tests/templatetags/testtags.py: no change ./tests/template_tests/templatetags/subpackage/__init__.py: no change ./tests/template_tests/templatetags/subpackage/echo.py: no change ./tests/test_client/__init__.py: no change ./tests/test_client/auth_backends.py: no change ./tests/test_client/test_conditional_content_removal.py: no change ./tests/test_client/test_fakepayload.py: no change ./tests/test_client/tests.py: no change ./tests/test_client/urls.py: no change ./tests/test_client/urls_middleware_urlconf.py: no change ./tests/test_client/views.py: no change ./tests/test_client_regress/__init__.py: no change ./tests/test_client_regress/auth_backends.py: no change ./tests/test_client_regress/context_processors.py: no change ./tests/test_client_regress/models.py: no change ./tests/test_client_regress/session.py: no change ./tests/test_client_regress/tests.py: no change ./tests/test_client_regress/urls.py: no change ./tests/test_client_regress/views.py: no change ./tests/test_exceptions/__init__.py: no change ./tests/test_exceptions/test_validation_error.py: no change ./tests/test_runner/__init__.py: no change ./tests/test_runner/models.py: no change ./tests/test_runner/runner.py: no change ./tests/test_runner/test_debug_sql.py: no change ./tests/test_runner/test_discover_runner.py: no change ./tests/test_runner/test_parallel.py: no change ./tests/test_runner/test_shuffler.py: no change ./tests/test_runner/tests.py: no change ./tests/test_runner_apps/__init__.py: no change ./tests/test_runner_apps/buffer/tests_buffer.py: no change ./tests/test_runner_apps/databases/__init__.py: no change ./tests/test_runner_apps/databases/tests.py: no change ./tests/test_runner_apps/failures/__init__.py: no change ./tests/test_runner_apps/failures/tests_failures.py: no change ./tests/test_runner_apps/sample/__init__.py: no change ./tests/test_runner_apps/sample/doctests.py: no change ./tests/test_runner_apps/sample/empty.py: no change ./tests/test_runner_apps/sample/pattern_tests.py: no change ./tests/test_runner_apps/sample/tests_sample.py: no change ./tests/test_runner_apps/sample/tests/__init__.py: no change ./tests/test_runner_apps/sample/tests/tests.py: no change ./tests/test_runner_apps/simple/__init__.py: no change ./tests/test_runner_apps/simple/tests.py: no change ./tests/test_runner_apps/tagged/__init__.py: no change ./tests/test_runner_apps/tagged/tests.py: no change ./tests/test_runner_apps/tagged/tests_inheritance.py: no change ./tests/test_runner_apps/tagged/tests_syntax_error.py: no change ./tests/test_utils/__init__.py: no change ./tests/test_utils/models.py: no change ./tests/test_utils/test_serializemixin.py: no change ./tests/test_utils/test_simpletestcase.py: no change ./tests/test_utils/test_testcase.py: no change ./tests/test_utils/test_transactiontestcase.py: no change ./tests/test_utils/tests.py: no change ./tests/test_utils/urls.py: no change ./tests/test_utils/views.py: no change ./tests/timezones/__init__.py: no change ./tests/timezones/admin.py: no change ./tests/timezones/forms.py: no change ./tests/timezones/models.py: no change ./tests/timezones/tests.py: no change ./tests/timezones/urls.py: no change ./tests/transaction_hooks/__init__.py: no change ./tests/transaction_hooks/models.py: no change ./tests/transaction_hooks/tests.py: no change ./tests/transactions/__init__.py: no change ./tests/transactions/models.py: no change ./tests/transactions/tests.py: no change ./tests/unmanaged_models/__init__.py: no change ./tests/unmanaged_models/models.py: no change ./tests/unmanaged_models/tests.py: no change ./tests/update/__init__.py: no change ./tests/update/models.py: no change ./tests/update/tests.py: no change ./tests/update_only_fields/__init__.py: no change ./tests/update_only_fields/models.py: no change ./tests/update_only_fields/tests.py: no change ./tests/urlpatterns/__init__.py: no change ./tests/urlpatterns/converter_urls.py: no change ./tests/urlpatterns/converters.py: no change ./tests/urlpatterns/included_urls.py: no change ./tests/urlpatterns/more_urls.py: no change ./tests/urlpatterns/path_base64_urls.py: no change ./tests/urlpatterns/path_dynamic_urls.py: no change ./tests/urlpatterns/path_same_name_urls.py: no change ./tests/urlpatterns/path_urls.py: no change ./tests/urlpatterns/test_resolvers.py: no change ./tests/urlpatterns/tests.py: no change ./tests/urlpatterns/views.py: no change ./tests/urlpatterns_reverse/__init__.py: no change ./tests/urlpatterns_reverse/erroneous_urls.py: no change ./tests/urlpatterns_reverse/extra_urls.py: no change ./tests/urlpatterns_reverse/included_app_urls.py: no change ./tests/urlpatterns_reverse/included_named_urls.py: no change ./tests/urlpatterns_reverse/included_named_urls2.py: no change ./tests/urlpatterns_reverse/included_namespace_urls.py: no change ./tests/urlpatterns_reverse/included_no_kwargs_urls.py: no change ./tests/urlpatterns_reverse/included_urls.py: no change ./tests/urlpatterns_reverse/included_urls2.py: no change ./tests/urlpatterns_reverse/method_view_urls.py: no change ./tests/urlpatterns_reverse/middleware.py: no change ./tests/urlpatterns_reverse/named_urls.py: no change ./tests/urlpatterns_reverse/named_urls_conflict.py: no change ./tests/urlpatterns_reverse/namespace_urls.py: no change ./tests/urlpatterns_reverse/nested_urls.py: no change ./tests/urlpatterns_reverse/no_urls.py: no change ./tests/urlpatterns_reverse/nonimported_module.py: no change ./tests/urlpatterns_reverse/reverse_lazy_urls.py: no change ./tests/urlpatterns_reverse/test_localeregexdescriptor.py: no change ./tests/urlpatterns_reverse/tests.py: no change ./tests/urlpatterns_reverse/urlconf_inner.py: no change ./tests/urlpatterns_reverse/urlconf_outer.py: no change ./tests/urlpatterns_reverse/urls.py: no change ./tests/urlpatterns_reverse/urls_error_handlers.py: no change ./tests/urlpatterns_reverse/urls_error_handlers_callables.py: no change ./tests/urlpatterns_reverse/urls_without_handlers.py: no change ./tests/urlpatterns_reverse/utils.py: no change ./tests/urlpatterns_reverse/views.py: no change ./tests/urlpatterns_reverse/views_broken.py: no change ./tests/urlpatterns_reverse/translations/__init__.py: no change ./tests/urlpatterns_reverse/translations/locale/__init__.py: no change ./tests/urlpatterns_reverse/translations/locale/de/__init__.py: no change ./tests/urlpatterns_reverse/translations/locale/fr/__init__.py: no change ./tests/user_commands/__init__.py: no change ./tests/user_commands/models.py: no change ./tests/user_commands/tests.py: no change ./tests/user_commands/urls.py: no change ./tests/user_commands/management/__init__.py: no change ./tests/user_commands/management/commands/__init__.py: no change ./tests/user_commands/management/commands/common_args.py: no change ./tests/user_commands/management/commands/dance.py: no change ./tests/user_commands/management/commands/hal.py: no change ./tests/user_commands/management/commands/mutually_exclusive_required.py: no change ./tests/user_commands/management/commands/mutually_exclusive_required_with_same_dest.py: no change ./tests/user_commands/management/commands/no_system_checks.py: no change ./tests/user_commands/management/commands/no_translations.py: no change ./tests/user_commands/management/commands/outputwrapper.py: no change ./tests/user_commands/management/commands/required_constant_option.py: no change ./tests/user_commands/management/commands/required_list_option.py: no change ./tests/user_commands/management/commands/required_option.py: no change ./tests/user_commands/management/commands/reverse_url.py: no change ./tests/user_commands/management/commands/set_option.py: no change ./tests/user_commands/management/commands/specific_system_checks.py: no change ./tests/user_commands/management/commands/subparser.py: no change ./tests/user_commands/management/commands/subparser_dest.py: no change ./tests/user_commands/management/commands/subparser_required.py: no change ./tests/user_commands/management/commands/subparser_vanilla.py: no change ./tests/user_commands/management/commands/transaction.py: no change ./tests/utils_tests/__init__.py: no change ./tests/utils_tests/deconstructible_classes.py: no change ./tests/utils_tests/models.py: no change ./tests/utils_tests/test_archive.py: no change ./tests/utils_tests/test_autoreload.py: no change ./tests/utils_tests/test_choices.py: no change ./tests/utils_tests/test_connection.py: no change ./tests/utils_tests/test_crypto.py: no change ./tests/utils_tests/test_datastructures.py: no change ./tests/utils_tests/test_dateformat.py: no change ./tests/utils_tests/test_dateparse.py: no change ./tests/utils_tests/test_deconstruct.py: no change ./tests/utils_tests/test_decorators.py: no change ./tests/utils_tests/test_duration.py: no change ./tests/utils_tests/test_encoding.py: no change ./tests/utils_tests/test_feedgenerator.py: no change ./tests/utils_tests/test_functional.py: no change ./tests/utils_tests/test_hashable.py: no change ./tests/utils_tests/test_html.py: no change ./tests/utils_tests/test_http.py: no change ./tests/utils_tests/test_inspect.py: no change ./tests/utils_tests/test_ipv6.py: no change ./tests/utils_tests/test_jslex.py: no change ./tests/utils_tests/test_lazyobject.py: no change ./tests/utils_tests/test_lorem_ipsum.py: no change ./tests/utils_tests/test_module_loading.py: no change ./tests/utils_tests/test_no_submodule.py: no change ./tests/utils_tests/test_numberformat.py: no change ./tests/utils_tests/test_os_utils.py: no change ./tests/utils_tests/test_regex_helper.py: no change ./tests/utils_tests/test_safestring.py: no change ./tests/utils_tests/test_simplelazyobject.py: no change ./tests/utils_tests/test_termcolors.py: no change ./tests/utils_tests/test_text.py: no change ./tests/utils_tests/test_timesince.py: no change ./tests/utils_tests/test_timezone.py: no change ./tests/utils_tests/test_tree.py: no change ./tests/utils_tests/utils.py: no change ./tests/utils_tests/test_module/__init__.py: no change ./tests/utils_tests/test_module/__main__.py: no change ./tests/utils_tests/test_module/another_bad_module.py: no change ./tests/utils_tests/test_module/another_good_module.py: no change ./tests/utils_tests/test_module/bad_module.py: no change ./tests/utils_tests/test_module/good_module.py: no change ./tests/utils_tests/test_module/main_module.py: no change ./tests/utils_tests/test_module/child_module/__init__.py: no change ./tests/utils_tests/test_module/child_module/grandchild_module.py: no change ./tests/validation/__init__.py: no change ./tests/validation/models.py: no change ./tests/validation/test_constraints.py: no change ./tests/validation/test_custom_messages.py: no change ./tests/validation/test_error_messages.py: no change ./tests/validation/test_picklable.py: no change ./tests/validation/test_unique.py: no change ./tests/validation/test_validators.py: no change ./tests/validation/tests.py: no change ./tests/validators/__init__.py: no change ./tests/validators/tests.py: no change ./tests/version/__init__.py: no change ./tests/version/tests.py: no change ./tests/view_tests/__init__.py: no change ./tests/view_tests/default_urls.py: no change ./tests/view_tests/generic_urls.py: no change ./tests/view_tests/models.py: no change ./tests/view_tests/regression_21530_urls.py: no change ./tests/view_tests/urls.py: no change ./tests/view_tests/views.py: no change ./tests/view_tests/app0/__init__.py: no change ./tests/view_tests/app1/__init__.py: no change ./tests/view_tests/app2/__init__.py: no change ./tests/view_tests/app3/__init__.py: no change ./tests/view_tests/app4/__init__.py: no change ./tests/view_tests/app5/__init__.py: no change ./tests/view_tests/templatetags/__init__.py: no change ./tests/view_tests/templatetags/debugtags.py: no change ./tests/view_tests/tests/__init__.py: no change ./tests/view_tests/tests/test_csrf.py: no change ./tests/view_tests/tests/test_debug.py: no change ./tests/view_tests/tests/test_defaults.py: no change ./tests/view_tests/tests/test_i18n.py: no change ./tests/view_tests/tests/test_json.py: no change ./tests/view_tests/tests/test_specials.py: no change ./tests/view_tests/tests/test_static.py: no change ./tests/wsgi/__init__.py: no change ./tests/wsgi/tests.py: no change ./tests/wsgi/urls.py: no change ./tests/wsgi/wsgi.py: no change ./tests/xor_lookups/__init__.py: no change ./tests/xor_lookups/models.py: no change ./tests/xor_lookups/tests.py: no change Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.EezCib running build running build_py creating build creating build/lib creating build/lib/django copying django/shortcuts.py -> build/lib/django copying django/__init__.py -> build/lib/django copying django/__main__.py -> build/lib/django creating 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/paginator.py -> build/lib/django/core copying django/core/__init__.py -> build/lib/django/core copying django/core/exceptions.py -> build/lib/django/core copying django/core/validators.py -> build/lib/django/core copying django/core/asgi.py -> build/lib/django/core copying django/core/wsgi.py -> build/lib/django/core 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/apps copying django/apps/config.py -> build/lib/django/apps copying django/apps/__init__.py -> build/lib/django/apps copying django/apps/registry.py -> build/lib/django/apps creating build/lib/django/contrib copying django/contrib/__init__.py -> build/lib/django/contrib creating build/lib/django/db copying django/db/transaction.py -> build/lib/django/db copying django/db/__init__.py -> build/lib/django/db copying django/db/utils.py -> build/lib/django/db creating build/lib/django/test copying django/test/signals.py -> build/lib/django/test copying django/test/client.py -> build/lib/django/test copying django/test/__init__.py -> build/lib/django/test copying django/test/html.py -> build/lib/django/test copying django/test/testcases.py -> build/lib/django/test copying django/test/selenium.py -> build/lib/django/test copying django/test/runner.py -> build/lib/django/test copying django/test/utils.py -> build/lib/django/test creating build/lib/django/views copying django/views/__init__.py -> build/lib/django/views copying django/views/debug.py -> build/lib/django/views copying django/views/static.py -> build/lib/django/views copying django/views/defaults.py -> build/lib/django/views copying django/views/csrf.py -> build/lib/django/views copying django/views/i18n.py -> build/lib/django/views creating build/lib/django/template copying django/template/loader_tags.py -> build/lib/django/template copying django/template/autoreload.py -> build/lib/django/template copying django/template/library.py -> build/lib/django/template copying django/template/context.py -> build/lib/django/template copying django/template/loader.py -> build/lib/django/template copying django/template/smartif.py -> build/lib/django/template copying django/template/__init__.py -> build/lib/django/template copying django/template/defaultfilters.py -> build/lib/django/template copying django/template/exceptions.py -> build/lib/django/template copying django/template/engine.py -> build/lib/django/template copying django/template/context_processors.py -> build/lib/django/template copying django/template/utils.py -> build/lib/django/template copying django/template/defaulttags.py -> build/lib/django/template copying django/template/response.py -> build/lib/django/template copying django/template/base.py -> build/lib/django/template creating build/lib/django/templatetags copying django/templatetags/l10n.py -> build/lib/django/templatetags copying django/templatetags/tz.py -> build/lib/django/templatetags copying django/templatetags/__init__.py -> build/lib/django/templatetags copying django/templatetags/static.py -> build/lib/django/templatetags copying django/templatetags/cache.py -> build/lib/django/templatetags copying django/templatetags/i18n.py -> build/lib/django/templatetags creating build/lib/django/forms copying django/forms/forms.py -> build/lib/django/forms copying django/forms/__init__.py -> build/lib/django/forms copying django/forms/fields.py -> build/lib/django/forms copying django/forms/formsets.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/models.py -> build/lib/django/forms copying django/forms/widgets.py -> build/lib/django/forms copying django/forms/boundfield.py -> build/lib/django/forms creating build/lib/django/middleware copying django/middleware/clickjacking.py -> build/lib/django/middleware copying django/middleware/__init__.py -> build/lib/django/middleware copying django/middleware/http.py -> build/lib/django/middleware copying django/middleware/gzip.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/locale.py -> build/lib/django/middleware copying django/middleware/cache.py -> build/lib/django/middleware copying django/middleware/security.py -> build/lib/django/middleware creating build/lib/django/http copying django/http/multipartparser.py -> build/lib/django/http copying django/http/cookie.py -> build/lib/django/http copying django/http/__init__.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/conf copying django/conf/__init__.py -> build/lib/django/conf copying django/conf/global_settings.py -> build/lib/django/conf creating build/lib/django/urls copying django/urls/resolvers.py -> build/lib/django/urls copying django/urls/__init__.py -> build/lib/django/urls copying django/urls/exceptions.py -> build/lib/django/urls copying django/urls/utils.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/base.py -> build/lib/django/urls creating build/lib/django/utils copying django/utils/jslex.py -> build/lib/django/utils copying django/utils/xmlutils.py -> build/lib/django/utils copying django/utils/crypto.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/version.py -> build/lib/django/utils copying django/utils/archive.py -> build/lib/django/utils copying django/utils/tree.py -> build/lib/django/utils copying django/utils/feedgenerator.py -> build/lib/django/utils copying django/utils/connection.py -> build/lib/django/utils copying django/utils/deconstruct.py -> build/lib/django/utils copying django/utils/hashable.py -> build/lib/django/utils copying django/utils/_os.py -> build/lib/django/utils copying django/utils/timezone.py -> build/lib/django/utils copying django/utils/numberformat.py -> build/lib/django/utils copying django/utils/choices.py -> build/lib/django/utils copying django/utils/log.py -> build/lib/django/utils copying django/utils/inspect.py -> build/lib/django/utils copying django/utils/__init__.py -> build/lib/django/utils copying django/utils/datastructures.py -> build/lib/django/utils copying django/utils/http.py -> build/lib/django/utils copying django/utils/html.py -> build/lib/django/utils copying django/utils/deprecation.py -> build/lib/django/utils copying django/utils/timesince.py -> build/lib/django/utils copying django/utils/functional.py -> build/lib/django/utils copying django/utils/ipv6.py -> build/lib/django/utils copying django/utils/regex_helper.py -> build/lib/django/utils copying django/utils/duration.py -> build/lib/django/utils copying django/utils/formats.py -> build/lib/django/utils copying django/utils/termcolors.py -> build/lib/django/utils copying django/utils/dateformat.py -> build/lib/django/utils copying django/utils/safestring.py -> build/lib/django/utils copying django/utils/decorators.py -> build/lib/django/utils copying django/utils/lorem_ipsum.py -> build/lib/django/utils copying django/utils/text.py -> build/lib/django/utils copying django/utils/itercompat.py -> build/lib/django/utils copying django/utils/encoding.py -> build/lib/django/utils copying django/utils/dates.py -> build/lib/django/utils copying django/utils/cache.py -> build/lib/django/utils copying django/utils/dateparse.py -> build/lib/django/utils copying django/utils/module_loading.py -> build/lib/django/utils 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/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/handlers copying django/core/handlers/exception.py -> 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/wsgi.py -> build/lib/django/core/handlers copying django/core/handlers/base.py -> build/lib/django/core/handlers creating build/lib/django/core/management copying django/core/management/sql.py -> build/lib/django/core/management copying django/core/management/color.py -> build/lib/django/core/management copying django/core/management/templates.py -> build/lib/django/core/management copying django/core/management/__init__.py -> build/lib/django/core/management copying django/core/management/utils.py -> build/lib/django/core/management copying django/core/management/base.py -> build/lib/django/core/management creating build/lib/django/core/files copying django/core/files/move.py -> build/lib/django/core/files copying django/core/files/__init__.py -> build/lib/django/core/files copying django/core/files/temp.py -> build/lib/django/core/files copying django/core/files/images.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 copying django/core/files/uploadedfile.py -> build/lib/django/core/files copying django/core/files/locks.py -> build/lib/django/core/files copying django/core/files/base.py -> build/lib/django/core/files creating build/lib/django/core/serializers copying django/core/serializers/json.py -> build/lib/django/core/serializers copying django/core/serializers/xml_serializer.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/__init__.py -> build/lib/django/core/serializers copying django/core/serializers/jsonl.py -> build/lib/django/core/serializers copying django/core/serializers/base.py -> build/lib/django/core/serializers creating build/lib/django/core/checks copying django/core/checks/messages.py -> build/lib/django/core/checks copying django/core/checks/translation.py -> build/lib/django/core/checks copying django/core/checks/model_checks.py -> build/lib/django/core/checks copying django/core/checks/templates.py -> build/lib/django/core/checks copying django/core/checks/urls.py -> build/lib/django/core/checks copying django/core/checks/__init__.py -> build/lib/django/core/checks copying django/core/checks/database.py -> build/lib/django/core/checks copying django/core/checks/async_checks.py -> build/lib/django/core/checks copying django/core/checks/files.py -> build/lib/django/core/checks copying django/core/checks/registry.py -> build/lib/django/core/checks copying django/core/checks/caches.py -> build/lib/django/core/checks 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/mail/backends copying django/core/mail/backends/console.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/smtp.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/__init__.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/base.py -> build/lib/django/core/mail/backends 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/redis.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/db.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/memcached.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/base.py -> build/lib/django/core/cache/backends creating build/lib/django/core/management/commands copying django/core/management/commands/optimizemigration.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/compilemessages.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/testserver.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/sendtestemail.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/__init__.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/migrate.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/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/test.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/startproject.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/runserver.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/startapp.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/sqlsequencereset.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/check.py -> build/lib/django/core/management/commands copying django/core/management/commands/makemigrations.py -> build/lib/django/core/management/commands creating build/lib/django/core/files/storage copying django/core/files/storage/mixins.py -> build/lib/django/core/files/storage copying django/core/files/storage/__init__.py -> build/lib/django/core/files/storage copying django/core/files/storage/handler.py -> build/lib/django/core/files/storage copying django/core/files/storage/memory.py -> build/lib/django/core/files/storage copying django/core/files/storage/base.py -> build/lib/django/core/files/storage copying django/core/files/storage/filesystem.py -> build/lib/django/core/files/storage 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/sessions.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/base.py -> build/lib/django/core/checks/security creating build/lib/django/core/checks/compatibility copying django/core/checks/compatibility/__init__.py -> build/lib/django/core/checks/compatibility copying django/core/checks/compatibility/django_4_0.py -> build/lib/django/core/checks/compatibility creating build/lib/django/contrib/syndication copying django/contrib/syndication/__init__.py -> build/lib/django/contrib/syndication copying django/contrib/syndication/views.py -> build/lib/django/contrib/syndication copying django/contrib/syndication/apps.py -> build/lib/django/contrib/syndication creating build/lib/django/contrib/sites copying django/contrib/sites/checks.py -> build/lib/django/contrib/sites copying django/contrib/sites/shortcuts.py -> build/lib/django/contrib/sites copying django/contrib/sites/managers.py -> build/lib/django/contrib/sites copying django/contrib/sites/__init__.py -> build/lib/django/contrib/sites copying django/contrib/sites/requests.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/management.py -> build/lib/django/contrib/sites copying django/contrib/sites/apps.py -> build/lib/django/contrib/sites copying django/contrib/sites/admin.py -> build/lib/django/contrib/sites creating build/lib/django/contrib/postgres copying django/contrib/postgres/functions.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/signals.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/serializers.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/operations.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/expressions.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/constraints.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/__init__.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/lookups.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/search.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/validators.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/utils.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/indexes.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/apps.py -> build/lib/django/contrib/postgres creating build/lib/django/contrib/gis copying django/contrib/gis/shortcuts.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/__init__.py -> build/lib/django/contrib/gis copying django/contrib/gis/feeds.py -> build/lib/django/contrib/gis copying django/contrib/gis/views.py -> build/lib/django/contrib/gis copying django/contrib/gis/apps.py -> build/lib/django/contrib/gis copying django/contrib/gis/ptr.py -> build/lib/django/contrib/gis creating build/lib/django/contrib/admin copying django/contrib/admin/checks.py -> build/lib/django/contrib/admin copying django/contrib/admin/sites.py -> build/lib/django/contrib/admin copying django/contrib/admin/forms.py -> build/lib/django/contrib/admin copying django/contrib/admin/__init__.py -> build/lib/django/contrib/admin copying django/contrib/admin/filters.py -> build/lib/django/contrib/admin copying django/contrib/admin/exceptions.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/helpers.py -> build/lib/django/contrib/admin copying django/contrib/admin/models.py -> build/lib/django/contrib/admin copying django/contrib/admin/actions.py -> build/lib/django/contrib/admin copying django/contrib/admin/decorators.py -> build/lib/django/contrib/admin copying django/contrib/admin/apps.py -> build/lib/django/contrib/admin copying django/contrib/admin/widgets.py -> build/lib/django/contrib/admin copying django/contrib/admin/options.py -> build/lib/django/contrib/admin creating build/lib/django/contrib/sitemaps copying django/contrib/sitemaps/__init__.py -> build/lib/django/contrib/sitemaps copying django/contrib/sitemaps/views.py -> build/lib/django/contrib/sitemaps copying django/contrib/sitemaps/apps.py -> build/lib/django/contrib/sitemaps creating build/lib/django/contrib/admindocs copying django/contrib/admindocs/urls.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/__init__.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/views.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/middleware.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/utils.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/apps.py -> build/lib/django/contrib/admindocs creating build/lib/django/contrib/auth copying django/contrib/auth/checks.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/mixins.py -> build/lib/django/contrib/auth copying django/contrib/auth/urls.py -> build/lib/django/contrib/auth copying django/contrib/auth/tokens.py -> build/lib/django/contrib/auth copying django/contrib/auth/forms.py -> build/lib/django/contrib/auth copying django/contrib/auth/base_user.py -> build/lib/django/contrib/auth copying django/contrib/auth/__init__.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 copying django/contrib/auth/context_processors.py -> build/lib/django/contrib/auth copying django/contrib/auth/backends.py -> build/lib/django/contrib/auth copying django/contrib/auth/middleware.py -> build/lib/django/contrib/auth copying django/contrib/auth/models.py -> build/lib/django/contrib/auth copying django/contrib/auth/decorators.py -> build/lib/django/contrib/auth copying django/contrib/auth/apps.py -> build/lib/django/contrib/auth copying django/contrib/auth/hashers.py -> build/lib/django/contrib/auth copying django/contrib/auth/admin.py -> build/lib/django/contrib/auth creating build/lib/django/contrib/sessions copying django/contrib/sessions/serializers.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/__init__.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/exceptions.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/base_session.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/apps.py -> build/lib/django/contrib/sessions creating build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/checks.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/urls.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/__init__.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/handlers.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/views.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/testing.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/utils.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/finders.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/storage.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/apps.py -> build/lib/django/contrib/staticfiles creating build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/checks.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/forms.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/__init__.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/fields.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/views.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/models.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/apps.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/prefetch.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/admin.py -> build/lib/django/contrib/contenttypes creating build/lib/django/contrib/flatpages copying django/contrib/flatpages/urls.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/forms.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/__init__.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/views.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/apps.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/sitemaps.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/admin.py -> build/lib/django/contrib/flatpages 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/views.py -> build/lib/django/contrib/messages copying django/contrib/messages/context_processors.py -> build/lib/django/contrib/messages copying django/contrib/messages/test.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/constants.py -> build/lib/django/contrib/messages copying django/contrib/messages/apps.py -> build/lib/django/contrib/messages 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/redirects copying django/contrib/redirects/__init__.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 copying django/contrib/redirects/apps.py -> build/lib/django/contrib/redirects copying django/contrib/redirects/admin.py -> build/lib/django/contrib/redirects creating build/lib/django/contrib/sites/migrations copying django/contrib/sites/migrations/__init__.py -> 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 creating build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/mixins.py -> build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/__init__.py -> build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/statistics.py -> build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/general.py -> build/lib/django/contrib/postgres/aggregates creating build/lib/django/contrib/postgres/forms copying django/contrib/postgres/forms/ranges.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/__init__.py -> build/lib/django/contrib/postgres/forms copying django/contrib/postgres/forms/hstore.py -> build/lib/django/contrib/postgres/forms creating build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/ranges.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/__init__.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/utils.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/jsonb.py -> build/lib/django/contrib/postgres/fields creating build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/srs.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/driver.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/__init__.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/datasource.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/envelope.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/geometries.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/base.py -> build/lib/django/contrib/gis/gdal creating build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/geometry.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/libgeos.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/__init__.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/prepared.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/polygon.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/point.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/mutable_list.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/base.py -> build/lib/django/contrib/gis/geos 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 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/management copying django/contrib/gis/management/__init__.py -> build/lib/django/contrib/gis/management 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/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/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/geoip2 copying django/contrib/gis/geoip2/__init__.py -> build/lib/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/resources.py -> build/lib/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/base.py -> build/lib/django/contrib/gis/geoip2 creating build/lib/django/contrib/gis/utils copying django/contrib/gis/utils/srs.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/__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/ogrinspect.py -> build/lib/django/contrib/gis/utils creating build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/srs.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/ds.py -> 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/errcheck.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/source.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/base.py -> build/lib/django/contrib/gis/gdal/raster creating build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/topology.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/__init__.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/errcheck.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/predicates.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/misc.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/coordseq.py -> build/lib/django/contrib/gis/geos/prototypes creating 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/__init__.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/lookups.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/proxy.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/aggregates.py -> build/lib/django/contrib/gis/db/models 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/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/db/backends/oracle copying django/contrib/gis/db/backends/oracle/schema.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/__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/features.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/introspection.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 creating 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 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 creating 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 copying django/contrib/gis/db/backends/mysql/operations.py -> 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/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/base.py -> build/lib/django/contrib/gis/db/backends/mysql creating 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 copying django/contrib/gis/db/backends/postgis/operations.py -> 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/pgraster.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/models.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/introspection.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 creating 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 copying django/contrib/gis/db/backends/spatialite/operations.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/__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/features.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/introspection.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 creating 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/__init__.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/admin/migrations copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/lib/django/contrib/admin/migrations copying django/contrib/admin/migrations/__init__.py -> 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/0003_logentry_add_action_flag_choices.py -> build/lib/django/contrib/admin/migrations creating build/lib/django/contrib/admin/views copying django/contrib/admin/views/main.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/__init__.py -> build/lib/django/contrib/admin/views copying django/contrib/admin/views/decorators.py -> build/lib/django/contrib/admin/views creating 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/log.py -> 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/base.py -> build/lib/django/contrib/admin/templatetags creating 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/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/__init__.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/0005_alter_user_last_login_null.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/0001_initial.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/0004_alter_user_username_opts.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/0002_alter_permission_name_max_length.py -> build/lib/django/contrib/auth/migrations 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/management/commands copying django/contrib/auth/management/commands/__init__.py -> build/lib/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/createsuperuser.py -> build/lib/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/changepassword.py -> build/lib/django/contrib/auth/management/commands 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/signed_cookies.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/cache.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/base.py -> build/lib/django/contrib/sessions/backends creating build/lib/django/contrib/sessions/migrations copying django/contrib/sessions/migrations/__init__.py -> build/lib/django/contrib/sessions/migrations copying django/contrib/sessions/migrations/0001_initial.py -> build/lib/django/contrib/sessions/migrations 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/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/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/runserver.py -> build/lib/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/findstatic.py -> build/lib/django/contrib/staticfiles/management/commands creating build/lib/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/__init__.py -> 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 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/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/__init__.py -> build/lib/django/contrib/flatpages/migrations copying django/contrib/flatpages/migrations/0001_initial.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/messages/storage copying django/contrib/messages/storage/cookie.py -> build/lib/django/contrib/messages/storage copying django/contrib/messages/storage/__init__.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 copying django/contrib/messages/storage/base.py -> build/lib/django/contrib/messages/storage 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/redirects/migrations copying django/contrib/redirects/migrations/__init__.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/0001_initial.py -> build/lib/django/contrib/redirects/migrations creating build/lib/django/db/models copying django/db/models/signals.py -> build/lib/django/db/models copying django/db/models/query_utils.py -> build/lib/django/db/models copying django/db/models/manager.py -> build/lib/django/db/models copying django/db/models/expressions.py -> build/lib/django/db/models copying django/db/models/constraints.py -> build/lib/django/db/models copying django/db/models/__init__.py -> build/lib/django/db/models copying django/db/models/lookups.py -> build/lib/django/db/models copying django/db/models/enums.py -> build/lib/django/db/models copying django/db/models/utils.py -> build/lib/django/db/models copying django/db/models/aggregates.py -> build/lib/django/db/models copying django/db/models/constants.py -> build/lib/django/db/models copying django/db/models/query.py -> build/lib/django/db/models copying django/db/models/indexes.py -> build/lib/django/db/models copying django/db/models/options.py -> build/lib/django/db/models copying django/db/models/deletion.py -> build/lib/django/db/models copying django/db/models/base.py -> build/lib/django/db/models creating build/lib/django/db/backends copying django/db/backends/signals.py -> build/lib/django/db/backends copying django/db/backends/__init__.py -> build/lib/django/db/backends copying django/db/backends/utils.py -> build/lib/django/db/backends copying django/db/backends/ddl_references.py -> build/lib/django/db/backends creating build/lib/django/db/migrations copying django/db/migrations/state.py -> build/lib/django/db/migrations copying django/db/migrations/graph.py -> build/lib/django/db/migrations copying django/db/migrations/migration.py -> build/lib/django/db/migrations copying django/db/migrations/loader.py -> build/lib/django/db/migrations copying django/db/migrations/__init__.py -> build/lib/django/db/migrations copying django/db/migrations/questioner.py -> build/lib/django/db/migrations copying django/db/migrations/exceptions.py -> build/lib/django/db/migrations copying django/db/migrations/optimizer.py -> build/lib/django/db/migrations copying django/db/migrations/writer.py -> build/lib/django/db/migrations copying django/db/migrations/utils.py -> build/lib/django/db/migrations copying django/db/migrations/autodetector.py -> build/lib/django/db/migrations copying django/db/migrations/recorder.py -> build/lib/django/db/migrations copying django/db/migrations/executor.py -> build/lib/django/db/migrations copying django/db/migrations/serializer.py -> build/lib/django/db/migrations creating build/lib/django/db/models/sql copying django/db/models/sql/where.py -> build/lib/django/db/models/sql copying django/db/models/sql/__init__.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/constants.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/query.py -> build/lib/django/db/models/sql copying django/db/models/sql/subqueries.py -> build/lib/django/db/models/sql creating build/lib/django/db/models/functions copying django/db/models/functions/window.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/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/__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/text.py -> build/lib/django/db/models/functions creating 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/related.py -> build/lib/django/db/models/fields copying django/db/models/fields/__init__.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/reverse_related.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/files.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/generated.py -> build/lib/django/db/models/fields creating build/lib/django/db/backends/oracle copying django/db/backends/oracle/functions.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/operations.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/__init__.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/validation.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/oracledb_any.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/utils.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/base.py -> build/lib/django/db/backends/oracle creating build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/_functions.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/schema.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/client.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/__init__.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/base.py -> build/lib/django/db/backends/sqlite3 creating build/lib/django/db/backends/base copying django/db/backends/base/schema.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/client.py -> build/lib/django/db/backends/base copying django/db/backends/base/__init__.py -> build/lib/django/db/backends/base copying django/db/backends/base/validation.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/base.py -> build/lib/django/db/backends/base creating build/lib/django/db/backends/mysql copying django/db/backends/mysql/schema.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/client.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/__init__.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/validation.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/compiler.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/base.py -> build/lib/django/db/backends/mysql creating build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/schema.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/client.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/__init__.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/psycopg_any.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/base.py -> build/lib/django/db/backends/postgresql 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/features.py -> build/lib/django/db/backends/dummy copying django/db/backends/dummy/base.py -> build/lib/django/db/backends/dummy 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/fields.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/models.py -> build/lib/django/db/migrations/operations copying django/db/migrations/operations/base.py -> build/lib/django/db/migrations/operations creating build/lib/django/views/generic copying django/views/generic/detail.py -> build/lib/django/views/generic copying django/views/generic/__init__.py -> build/lib/django/views/generic copying django/views/generic/list.py -> build/lib/django/views/generic copying django/views/generic/edit.py -> build/lib/django/views/generic copying django/views/generic/dates.py -> build/lib/django/views/generic copying django/views/generic/base.py -> build/lib/django/views/generic creating build/lib/django/views/decorators copying django/views/decorators/clickjacking.py -> build/lib/django/views/decorators copying django/views/decorators/__init__.py -> build/lib/django/views/decorators copying django/views/decorators/http.py -> build/lib/django/views/decorators copying django/views/decorators/gzip.py -> build/lib/django/views/decorators copying django/views/decorators/debug.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/cache.py -> build/lib/django/views/decorators copying django/views/decorators/vary.py -> build/lib/django/views/decorators creating build/lib/django/template/backends copying django/template/backends/django.py -> build/lib/django/template/backends copying django/template/backends/__init__.py -> build/lib/django/template/backends copying django/template/backends/dummy.py -> build/lib/django/template/backends copying django/template/backends/utils.py -> build/lib/django/template/backends copying django/template/backends/jinja2.py -> build/lib/django/template/backends copying django/template/backends/base.py -> build/lib/django/template/backends creating build/lib/django/template/loaders copying django/template/loaders/cached.py -> 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/locmem.py -> build/lib/django/template/loaders copying django/template/loaders/base.py -> build/lib/django/template/loaders copying django/template/loaders/filesystem.py -> build/lib/django/template/loaders creating build/lib/django/conf/urls copying django/conf/urls/__init__.py -> build/lib/django/conf/urls copying django/conf/urls/static.py -> build/lib/django/conf/urls copying django/conf/urls/i18n.py -> build/lib/django/conf/urls creating build/lib/django/conf/locale copying django/conf/locale/__init__.py -> build/lib/django/conf/locale creating build/lib/django/conf/locale/fr_CH copying django/conf/locale/fr_CH/__init__.py -> build/lib/django/conf/locale/fr_CH copying django/conf/locale/fr_CH/formats.py -> build/lib/django/conf/locale/fr_CH 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/en_IE copying django/conf/locale/en_IE/__init__.py -> build/lib/django/conf/locale/en_IE copying django/conf/locale/en_IE/formats.py -> build/lib/django/conf/locale/en_IE 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/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/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/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/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/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/fr_BE copying django/conf/locale/fr_BE/__init__.py -> build/lib/django/conf/locale/fr_BE copying django/conf/locale/fr_BE/formats.py -> build/lib/django/conf/locale/fr_BE 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/ms copying django/conf/locale/ms/__init__.py -> build/lib/django/conf/locale/ms copying django/conf/locale/ms/formats.py -> build/lib/django/conf/locale/ms 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/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/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/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/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/ug copying django/conf/locale/ug/__init__.py -> build/lib/django/conf/locale/ug copying django/conf/locale/ug/formats.py -> build/lib/django/conf/locale/ug 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/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/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/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/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/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/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/ckb copying django/conf/locale/ckb/__init__.py -> build/lib/django/conf/locale/ckb copying django/conf/locale/ckb/formats.py -> build/lib/django/conf/locale/ckb 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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_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/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/fr_CA copying django/conf/locale/fr_CA/__init__.py -> build/lib/django/conf/locale/fr_CA copying django/conf/locale/fr_CA/formats.py -> build/lib/django/conf/locale/fr_CA 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/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/utils/translation copying django/utils/translation/trans_real.py -> build/lib/django/utils/translation copying django/utils/translation/reloader.py -> build/lib/django/utils/translation copying django/utils/translation/__init__.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 running egg_info creating Django.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 writing manifest file 'Django.egg-info/SOURCES.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/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.app_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.app_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.app_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.app_template' to be distributed and are already explicitly excluding 'django.conf.app_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.app_template.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.app_template.migrations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.app_template.migrations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.app_template.migrations' to be distributed and are already explicitly excluding 'django.conf.app_template.migrations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ig.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ig.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ig.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ig.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ig.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.project_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.project_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.project_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.project_template' to be distributed and are already explicitly excluding 'django.conf.project_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.project_template.project_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.project_template.project_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.project_template.project_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.project_template.project_name' to be distributed and are already explicitly excluding 'django.conf.project_template.project_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.am.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.am.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.am.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.am.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.am.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.css' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.css.vendor.select2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.css.vendor.select2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.css.vendor.select2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.css.vendor.select2' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.css.vendor.select2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.img' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.img.gis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.img.gis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.img.gis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.img.gis' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.img.gis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.admin' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.jquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.jquery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.jquery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.jquery' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.jquery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.select2' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2.i18n' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.select2.i18n' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2.i18n' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.xregexp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.xregexp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.xregexp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.xregexp' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.xregexp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.auth.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.auth.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.auth.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.auth.user' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.auth.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.edit_inline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.edit_inline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.edit_inline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.edit_inline' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.edit_inline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.includes' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.widgets' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.registration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.registration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.registration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.registration' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.registration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.templates.admin_doc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.templates.admin_doc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.templates.admin_doc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.templates.admin_doc' to be distributed and are already explicitly excluding 'django.contrib.admindocs.templates.admin_doc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.templates.auth.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.templates.auth.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.templates.auth.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.templates.auth.widgets' to be distributed and are already explicitly excluding 'django.contrib.auth.templates.auth.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.templates.registration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.templates.registration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.templates.registration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.templates.registration' to be distributed and are already explicitly excluding 'django.contrib.auth.templates.registration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.static.gis.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.static.gis.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.static.gis.css' to be distributed and are already explicitly excluding 'django.contrib.gis.static.gis.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.static.gis.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.static.gis.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.static.gis.img' to be distributed and are already explicitly excluding 'django.contrib.gis.static.gis.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.static.gis.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.static.gis.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.static.gis.js' to be distributed and are already explicitly excluding 'django.contrib.gis.static.gis.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.templates.gis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.templates.gis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.templates.gis' to be distributed and are already explicitly excluding 'django.contrib.gis.templates.gis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis.kml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.templates.gis.kml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.templates.gis.kml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.templates.gis.kml' to be distributed and are already explicitly excluding 'django.contrib.gis.templates.gis.kml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.jinja2.postgres.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.jinja2.postgres.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.jinja2.postgres.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.jinja2.postgres.widgets' to be distributed and are already explicitly excluding 'django.contrib.postgres.jinja2.postgres.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.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.postgres.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.postgres.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent 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.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more 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.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.templates.postgres.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.templates.postgres.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.templates.postgres.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.templates.postgres.widgets' to be distributed and are already explicitly excluding 'django.contrib.postgres.templates.postgres.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sitemaps.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sitemaps.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sitemaps.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sitemaps.templates' to be distributed and are already explicitly excluding 'django.contrib.sitemaps.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.errors.dict' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.errors.dict' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.errors.dict' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.errors.dict' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.errors.dict' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.errors.list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.errors.list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.errors.list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.errors.list' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.errors.list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.formsets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.formsets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.formsets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.formsets' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.formsets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.widgets' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.errors.dict' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.errors.dict' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.errors.dict' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.errors.dict' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.errors.dict' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.errors.list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.errors.list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.errors.list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.errors.list' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.errors.list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.formsets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.formsets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.formsets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.formsets' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.formsets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.widgets' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _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) copying django/dispatch/license.txt -> build/lib/django/dispatch creating build/lib/django/views/templates copying django/views/templates/csrf_403.html -> build/lib/django/views/templates copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates copying django/views/templates/directory_index.html -> build/lib/django/views/templates copying django/views/templates/i18n_catalog.js -> 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/forms/jinja2 creating build/lib/django/forms/jinja2/django creating build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/attrs.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/div.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/field.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/label.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/p.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/table.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/ul.html -> build/lib/django/forms/jinja2/django/forms creating build/lib/django/forms/jinja2/django/forms/errors creating build/lib/django/forms/jinja2/django/forms/errors/dict copying django/forms/jinja2/django/forms/errors/dict/default.html -> build/lib/django/forms/jinja2/django/forms/errors/dict copying django/forms/jinja2/django/forms/errors/dict/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/dict copying django/forms/jinja2/django/forms/errors/dict/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/dict creating build/lib/django/forms/jinja2/django/forms/errors/list copying django/forms/jinja2/django/forms/errors/list/default.html -> build/lib/django/forms/jinja2/django/forms/errors/list copying django/forms/jinja2/django/forms/errors/list/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/list copying django/forms/jinja2/django/forms/errors/list/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/list creating build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/div.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/p.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/table.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/ul.html -> build/lib/django/forms/jinja2/django/forms/formsets 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 copying django/forms/templates/django/forms/attrs.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/div.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/field.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/label.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/p.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/table.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/ul.html -> build/lib/django/forms/templates/django/forms creating build/lib/django/forms/templates/django/forms/errors creating build/lib/django/forms/templates/django/forms/errors/dict copying django/forms/templates/django/forms/errors/dict/default.html -> build/lib/django/forms/templates/django/forms/errors/dict copying django/forms/templates/django/forms/errors/dict/text.txt -> build/lib/django/forms/templates/django/forms/errors/dict copying django/forms/templates/django/forms/errors/dict/ul.html -> build/lib/django/forms/templates/django/forms/errors/dict creating build/lib/django/forms/templates/django/forms/errors/list copying django/forms/templates/django/forms/errors/list/default.html -> build/lib/django/forms/templates/django/forms/errors/list copying django/forms/templates/django/forms/errors/list/text.txt -> build/lib/django/forms/templates/django/forms/errors/list copying django/forms/templates/django/forms/errors/list/ul.html -> build/lib/django/forms/templates/django/forms/errors/list creating build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/div.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/p.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/table.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/ul.html -> build/lib/django/forms/templates/django/forms/formsets 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/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 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/ckb creating build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ckb/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/ms creating build/lib/django/contrib/sites/locale/ms/LC_MESSAGES copying django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES copying django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ms/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/ug creating build/lib/django/contrib/sites/locale/ug/LC_MESSAGES copying django/contrib/sites/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ug/LC_MESSAGES copying django/contrib/sites/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ug/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 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/ckb creating build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ckb/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/en_AU creating build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en_AU/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/mr creating build/lib/django/contrib/postgres/locale/mr/LC_MESSAGES copying django/contrib/postgres/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mr/LC_MESSAGES copying django/contrib/postgres/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mr/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ms creating build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ms/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/nn creating build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nn/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/ug creating build/lib/django/contrib/postgres/locale/ug/LC_MESSAGES copying django/contrib/postgres/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ug/LC_MESSAGES copying django/contrib/postgres/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ug/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/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/ckb creating build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ckb/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/ms creating build/lib/django/contrib/gis/locale/ms/LC_MESSAGES copying django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES copying django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ms/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/ug creating build/lib/django/contrib/gis/locale/ug/LC_MESSAGES copying django/contrib/gis/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ug/LC_MESSAGES copying django/contrib/gis/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ug/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/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/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/ckb creating build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ckb/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/ms creating build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ms/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/tk creating build/lib/django/contrib/admin/locale/tk/LC_MESSAGES copying django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES copying django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tk/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/ug creating build/lib/django/contrib/admin/locale/ug/LC_MESSAGES copying django/contrib/admin/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ug/LC_MESSAGES copying django/contrib/admin/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ug/LC_MESSAGES copying django/contrib/admin/locale/ug/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ug/LC_MESSAGES copying django/contrib/admin/locale/ug/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ug/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/dark_mode.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/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/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-hidelink.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/filters.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/theme.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/color_theme_toggle.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/date.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/time.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/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/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/ckb creating build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ckb/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/ms creating build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ms/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/ug creating build/lib/django/contrib/admindocs/locale/ug/LC_MESSAGES copying django/contrib/admindocs/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ug/LC_MESSAGES copying django/contrib/admindocs/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ug/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/ckb creating build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ckb/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/ms creating build/lib/django/contrib/auth/locale/ms/LC_MESSAGES copying django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES copying django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ms/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/ug creating build/lib/django/contrib/auth/locale/ug/LC_MESSAGES copying django/contrib/auth/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ug/LC_MESSAGES copying django/contrib/auth/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ug/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/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/ckb creating build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ckb/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/ms creating build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ms/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/ug creating build/lib/django/contrib/sessions/locale/ug/LC_MESSAGES copying django/contrib/sessions/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ug/LC_MESSAGES copying django/contrib/sessions/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ug/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/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/ckb creating build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ckb/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/ms creating build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ms/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/ug creating build/lib/django/contrib/contenttypes/locale/ug/LC_MESSAGES copying django/contrib/contenttypes/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ug/LC_MESSAGES copying django/contrib/contenttypes/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ug/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/ckb creating build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ckb/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/ms creating build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ms/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/ug creating build/lib/django/contrib/flatpages/locale/ug/LC_MESSAGES copying django/contrib/flatpages/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ug/LC_MESSAGES copying django/contrib/flatpages/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ug/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/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/ckb creating build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ckb/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/tk creating build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tk/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/ug creating build/lib/django/contrib/humanize/locale/ug/LC_MESSAGES copying django/contrib/humanize/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ug/LC_MESSAGES copying django/contrib/humanize/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ug/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/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/ckb creating build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ckb/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/ms creating build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ms/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/ug creating build/lib/django/contrib/redirects/locale/ug/LC_MESSAGES copying django/contrib/redirects/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ug/LC_MESSAGES copying django/contrib/redirects/locale/ug/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ug/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 copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/ms/LC_MESSAGES copying django/conf/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ms/LC_MESSAGES copying django/conf/locale/ms/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ms/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/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/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/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/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/ug/LC_MESSAGES copying django/conf/locale/ug/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ug/LC_MESSAGES copying django/conf/locale/ug/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ug/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/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/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/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/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/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/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/ckb/LC_MESSAGES copying django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ckb/LC_MESSAGES copying django/conf/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ckb/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.AJ7EfX + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch ++ dirname /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch + cd django-5.0.8 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-ld -Wl,--build-id=sha1' + /usr/bin/python3 setup.py install -O1 --skip-build --root /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch running install /usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core copying build/lib/django/core/signals.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core copying build/lib/django/core/signing.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/console.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/smtp.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/dummy.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/filebased.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/locmem.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/backends/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends copying build/lib/django/core/mail/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail copying build/lib/django/core/mail/message.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail copying build/lib/django/core/mail/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail copying build/lib/django/core/paginator.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/redis.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/dummy.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/db.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/memcached.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/filebased.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/locmem.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/backends/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends copying build/lib/django/core/cache/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache copying build/lib/django/core/cache/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache copying build/lib/django/core/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers copying build/lib/django/core/handlers/exception.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers copying build/lib/django/core/handlers/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers copying build/lib/django/core/handlers/asgi.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers copying build/lib/django/core/handlers/wsgi.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers copying build/lib/django/core/handlers/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management copying build/lib/django/core/management/sql.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management copying build/lib/django/core/management/color.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management copying build/lib/django/core/management/templates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/optimizemigration.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/flush.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/compilemessages.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/showmigrations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/testserver.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/dumpdata.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/sendtestemail.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/inspectdb.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/loaddata.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/migrate.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/makemessages.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/sqlflush.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/sqlmigrate.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/test.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/squashmigrations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/startproject.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/diffsettings.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/runserver.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/createcachetable.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/startapp.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/dbshell.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/sqlsequencereset.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/shell.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/check.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/commands/makemigrations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands copying build/lib/django/core/management/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management copying build/lib/django/core/management/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management copying build/lib/django/core/management/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management copying build/lib/django/core/exceptions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core copying build/lib/django/core/validators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/move.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/temp.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/images.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/uploadhandler.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/uploadedfile.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/storage/mixins.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/storage/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/storage/handler.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/storage/memory.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/storage/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/storage/filesystem.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage copying build/lib/django/core/files/locks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/files/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files copying build/lib/django/core/asgi.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/json.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/xml_serializer.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/python.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/pyyaml.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/jsonl.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/serializers/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers copying build/lib/django/core/wsgi.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/messages.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/translation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/model_checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/templates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/urls.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security copying build/lib/django/core/checks/security/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security copying build/lib/django/core/checks/security/sessions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security copying build/lib/django/core/checks/security/csrf.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security copying build/lib/django/core/checks/security/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security copying build/lib/django/core/checks/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/database.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/async_checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/files.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/registry.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks copying build/lib/django/core/checks/caches.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/compatibility copying build/lib/django/core/checks/compatibility/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/compatibility copying build/lib/django/core/checks/compatibility/django_4_0.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/compatibility creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/servers copying build/lib/django/core/servers/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/servers copying build/lib/django/core/servers/basehttp.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/servers creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/dispatch copying build/lib/django/dispatch/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/dispatch copying build/lib/django/dispatch/license.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/dispatch copying build/lib/django/dispatch/dispatcher.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/dispatch copying build/lib/django/shortcuts.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps copying build/lib/django/apps/config.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps copying build/lib/django/apps/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps copying build/lib/django/apps/registry.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication copying build/lib/django/contrib/syndication/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication copying build/lib/django/contrib/syndication/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication copying build/lib/django/contrib/syndication/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/shortcuts.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations copying build/lib/django/contrib/sites/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations copying build/lib/django/contrib/sites/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations copying build/lib/django/contrib/sites/managers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/requests.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/management.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites copying build/lib/django/contrib/sites/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/af/LC_MESSAGES copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/af/LC_MESSAGES copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/os/LC_MESSAGES copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/os/LC_MESSAGES copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/th/LC_MESSAGES copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/th/LC_MESSAGES copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/he/LC_MESSAGES copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/he/LC_MESSAGES copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/is/LC_MESSAGES copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/is/LC_MESSAGES copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/da/LC_MESSAGES copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/da/LC_MESSAGES copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ug/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ug/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/br/LC_MESSAGES copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/br/LC_MESSAGES copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/it/LC_MESSAGES copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/it/LC_MESSAGES copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/de/LC_MESSAGES copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/de/LC_MESSAGES copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/my/LC_MESSAGES copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/my/LC_MESSAGES copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/id/LC_MESSAGES copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/id/LC_MESSAGES copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/az/LC_MESSAGES copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/az/LC_MESSAGES copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/et/LC_MESSAGES copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/et/LC_MESSAGES copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/io/LC_MESSAGES copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/io/LC_MESSAGES copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/te/LC_MESSAGES copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/te/LC_MESSAGES copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/el/LC_MESSAGES copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/el/LC_MESSAGES copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/km/LC_MESSAGES copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/km/LC_MESSAGES copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/be/LC_MESSAGES copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/be/LC_MESSAGES copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/locale/be/LC_MESSAGES copying build/lib/django/contrib/sites/admin.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/functions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/signals.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/serializers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/expressions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/mixins.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/statistics.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/general.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/constraints.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/lookups.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/templates creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/templates/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/templates/postgres/widgets copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/templates/postgres/widgets copying build/lib/django/contrib/postgres/search.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres copying build/lib/django/contrib/postgres/validators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/ranges.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/array.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/hstore.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/ranges.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/array.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/citext.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/hstore.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/jsonb.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/indexes.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/jinja2 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/jinja2/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/jinja2/postgres/widgets copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/jinja2/postgres/widgets copying build/lib/django/contrib/postgres/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ia/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ia/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ne/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ne/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/af/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/af/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ja/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ja/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sq/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sq/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/he/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/he/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/is/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/is/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ka/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ka/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ro/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ro/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ky/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ky/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/da/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/da/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ml/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ml/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/kk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/kk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ms/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ms/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uz/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uz/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ko/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ko/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ug/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ug/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ca/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ca/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/it/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/it/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/de/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/de/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hy/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hy/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ru/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ru/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/id/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/id/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/az/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/az/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/et/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/et/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/cs/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/cs/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fi/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fi/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fa/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fa/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/bg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/bg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gd/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gd/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/el/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/el/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eo/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eo/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/be/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/be/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/locale/be/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/srs.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/libgdal.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/driver.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/error.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/band.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/source.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/const.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/feature.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/datasource.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/geomtype.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/envelope.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/layer.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/geometries.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/field.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/LICENSE -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal copying build/lib/django/contrib/gis/shortcuts.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis copying build/lib/django/contrib/gis/geometry.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis copying build/lib/django/contrib/gis/measure.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/geometry.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/linestring.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/io.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/libgeos.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/error.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/prepared.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/io.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/polygon.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/collections.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/point.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/factory.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/mutable_list.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/coordseq.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/LICENSE -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/admin copying build/lib/django/contrib/gis/admin/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/admin copying build/lib/django/contrib/gis/admin/options.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/css copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/css creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/js copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/js creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/static/gis/img creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/functions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/sql copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/sql copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/sql copying build/lib/django/contrib/gis/db/models/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/fields.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/lookups.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/proxy.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/aggregates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db copying build/lib/django/contrib/gis/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates/gis copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates/gis/kml copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates/gis/kml copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates/gis/kml copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/templates/gis copying build/lib/django/contrib/gis/feeds.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/sitemaps/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/sitemaps/kml.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/sitemaps/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms copying build/lib/django/contrib/gis/forms/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms copying build/lib/django/contrib/gis/forms/fields.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms copying build/lib/django/contrib/gis/forms/widgets.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms copying build/lib/django/contrib/gis/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/serializers copying build/lib/django/contrib/gis/serializers/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/serializers copying build/lib/django/contrib/gis/serializers/geojson.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/serializers copying build/lib/django/contrib/gis/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2 copying build/lib/django/contrib/gis/geoip2/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2 copying build/lib/django/contrib/gis/geoip2/resources.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2 copying build/lib/django/contrib/gis/geoip2/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sw/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sw/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ia/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ia/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ne/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ne/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/af/LC_MESSAGES copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/af/LC_MESSAGES copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ja/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ja/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/os/LC_MESSAGES copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/os/LC_MESSAGES copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/th/LC_MESSAGES copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/th/LC_MESSAGES copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sq/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sq/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/he/LC_MESSAGES copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/he/LC_MESSAGES copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/is/LC_MESSAGES copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/is/LC_MESSAGES copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ka/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ka/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ro/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ro/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ky/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ky/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ta/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ta/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/udm/LC_MESSAGES copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/udm/LC_MESSAGES copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ast/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ast/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/da/LC_MESSAGES copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/da/LC_MESSAGES copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ml/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ml/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ms/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ms/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ga/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ga/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ko/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ko/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ug/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ug/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/br/LC_MESSAGES copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/br/LC_MESSAGES copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ca/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ca/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/it/LC_MESSAGES copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/it/LC_MESSAGES copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ur/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ur/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/de/LC_MESSAGES copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/de/LC_MESSAGES copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/my/LC_MESSAGES copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/my/LC_MESSAGES copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ru/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ru/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/id/LC_MESSAGES copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/id/LC_MESSAGES copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/vi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/vi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/az/LC_MESSAGES copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/az/LC_MESSAGES copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/et/LC_MESSAGES copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/et/LC_MESSAGES copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/io/LC_MESSAGES copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/io/LC_MESSAGES copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gd/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gd/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/uk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/uk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/te/LC_MESSAGES copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/te/LC_MESSAGES copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/el/LC_MESSAGES copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/el/LC_MESSAGES copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/km/LC_MESSAGES copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/km/LC_MESSAGES copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eo/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eo/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/be/LC_MESSAGES copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/be/LC_MESSAGES copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/locale/be/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/srs.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/ogrinfo.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/layermapping.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/ogrinspect.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils copying build/lib/django/contrib/gis/ptr.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/sites.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations copying build/lib/django/contrib/admin/forms.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/login.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css/vendor creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/base.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/forms.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/dark_mode.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/css creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/xregexp creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2 copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2 copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/select2 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/actions.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/admin copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/admin copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js/admin copying build/lib/django/contrib/admin/static/admin/js/core.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/filters.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/theme.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/js creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/search.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img/gis copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img/gis copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img/gis copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/README.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-hidelink.svg -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/filters.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/registration creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/includes copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/includes copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/includes copying build/lib/django/contrib/admin/templates/admin/change_form.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/object_history.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_list.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/search_form.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/500.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/color_theme_toggle.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/login.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/actions.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/filter.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/date.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/time.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/404.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/auth creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/auth/user copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/auth/user copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/auth/user copying build/lib/django/contrib/admin/templates/admin/base_site.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/app_index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/app_list.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/edit_inline copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/edit_inline copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin/edit_inline copying build/lib/django/contrib/admin/templates/admin/base.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/pagination.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templates/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views copying build/lib/django/contrib/admin/views/main.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views copying build/lib/django/contrib/admin/views/autocomplete.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views copying build/lib/django/contrib/admin/views/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views copying build/lib/django/contrib/admin/views/decorators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views copying build/lib/django/contrib/admin/exceptions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/log.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/admin_list.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/tests.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/helpers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/actions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/decorators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/widgets.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin copying build/lib/django/contrib/admin/options.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/am creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/am/LC_MESSAGES copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/am/LC_MESSAGES copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/am/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ug/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ug/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ug/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ug/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ug/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ug/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps copying build/lib/django/contrib/sitemaps/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps/templates copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps/templates copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps/templates copying build/lib/django/contrib/sitemaps/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps copying build/lib/django/contrib/sitemaps/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs copying build/lib/django/contrib/admindocs/urls.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs copying build/lib/django/contrib/admindocs/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs copying build/lib/django/contrib/admindocs/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs copying build/lib/django/contrib/admindocs/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs copying build/lib/django/contrib/admindocs/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/af/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/af/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/os/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/os/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/th/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/th/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/he/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/he/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/is/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/is/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/da/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/da/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ug/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ug/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/br/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/br/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/it/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/it/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/de/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/de/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/my/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/my/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/id/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/id/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/az/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/az/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/et/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/et/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/io/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/io/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/te/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/te/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/el/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/el/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/km/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/km/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/be/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/be/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/locale/be/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/password_validation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/signals.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/mixins.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations copying build/lib/django/contrib/auth/urls.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/tokens.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/forms.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/base_user.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/handlers copying build/lib/django/contrib/auth/handlers/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/handlers copying build/lib/django/contrib/auth/handlers/modwsgi.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/handlers creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/templates creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/templates/registration copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/templates/registration creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/templates/auth creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/templates/auth/widgets copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/templates/auth/widgets creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/commands/changepassword.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management copying build/lib/django/contrib/auth/validators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/context_processors.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/backends.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/common-passwords.txt.gz -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/decorators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth copying build/lib/django/contrib/auth/hashers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sw/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sw/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ia/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ia/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ne/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ne/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/af/LC_MESSAGES copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/af/LC_MESSAGES copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ja/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ja/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/os/LC_MESSAGES copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/os/LC_MESSAGES copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/th/LC_MESSAGES copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/th/LC_MESSAGES copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sq/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sq/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/he/LC_MESSAGES copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/he/LC_MESSAGES copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/is/LC_MESSAGES copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/is/LC_MESSAGES copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ka/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ka/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ro/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ro/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ky/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ky/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ta/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ta/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/udm/LC_MESSAGES copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/udm/LC_MESSAGES copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ast/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ast/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/da/LC_MESSAGES copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/da/LC_MESSAGES copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ml/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ml/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ms/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ms/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uz/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uz/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ga/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ga/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ko/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ko/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ug/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ug/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/br/LC_MESSAGES copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/br/LC_MESSAGES copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ca/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ca/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/it/LC_MESSAGES copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/it/LC_MESSAGES copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ur/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ur/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/de/LC_MESSAGES copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/de/LC_MESSAGES copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/my/LC_MESSAGES copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/my/LC_MESSAGES copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ru/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ru/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/id/LC_MESSAGES copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/id/LC_MESSAGES copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kab/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kab/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/vi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/vi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/az/LC_MESSAGES copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/az/LC_MESSAGES copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/et/LC_MESSAGES copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/et/LC_MESSAGES copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/io/LC_MESSAGES copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/io/LC_MESSAGES copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gd/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gd/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/te/LC_MESSAGES copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/te/LC_MESSAGES copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/el/LC_MESSAGES copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/el/LC_MESSAGES copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/km/LC_MESSAGES copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/km/LC_MESSAGES copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eo/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eo/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/be/LC_MESSAGES copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/be/LC_MESSAGES copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/locale/be/LC_MESSAGES copying build/lib/django/contrib/auth/admin.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions copying build/lib/django/contrib/sessions/serializers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/cached_db.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/db.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/file.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/cache.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/migrations copying build/lib/django/contrib/sessions/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/migrations copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/migrations copying build/lib/django/contrib/sessions/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management/commands copying build/lib/django/contrib/sessions/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management/commands copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management/commands copying build/lib/django/contrib/sessions/management/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management copying build/lib/django/contrib/sessions/exceptions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions copying build/lib/django/contrib/sessions/base_session.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions copying build/lib/django/contrib/sessions/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions copying build/lib/django/contrib/sessions/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions copying build/lib/django/contrib/sessions/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/af/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/af/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/os/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/os/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/th/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/th/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/he/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/he/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/is/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/is/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/da/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/da/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ug/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ug/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/br/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/br/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/it/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/it/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/de/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/de/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/my/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/my/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/id/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/id/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/az/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/az/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/et/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/et/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/io/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/io/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/te/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/te/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/el/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/el/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/km/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/km/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/be/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/be/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/locale/be/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/urls.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management copying build/lib/django/contrib/staticfiles/handlers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/testing.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/finders.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/storage.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/checks.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/forms.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/fields.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management/commands copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management/commands copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management/commands copying build/lib/django/contrib/contenttypes/management/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management copying build/lib/django/contrib/contenttypes/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/prefetch.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/af/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/af/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/os/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/os/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/th/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/th/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/he/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/he/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/is/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/is/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/da/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/da/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ug/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ug/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/br/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/br/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/it/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/it/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/de/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/de/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/my/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/my/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/id/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/id/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/az/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/az/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/et/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/et/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/io/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/io/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/te/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/te/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/el/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/el/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/km/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/km/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/be/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/be/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/locale/be/LC_MESSAGES copying build/lib/django/contrib/contenttypes/admin.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/migrations copying build/lib/django/contrib/flatpages/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/migrations copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/migrations copying build/lib/django/contrib/flatpages/urls.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages copying build/lib/django/contrib/flatpages/forms.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages copying build/lib/django/contrib/flatpages/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/templatetags copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/templatetags copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/templatetags copying build/lib/django/contrib/flatpages/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages copying build/lib/django/contrib/flatpages/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages copying build/lib/django/contrib/flatpages/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages copying build/lib/django/contrib/flatpages/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sw/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sw/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ia/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ia/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ne/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ne/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/af/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/af/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ja/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ja/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/os/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/os/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/th/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/th/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sq/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sq/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/he/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/he/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/is/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/is/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ka/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ka/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ro/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ro/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ky/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ky/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ta/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ta/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/udm/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/udm/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ast/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ast/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/da/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/da/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ml/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ml/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ms/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ms/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ga/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ga/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ko/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ko/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ug/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ug/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/br/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/br/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ca/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ca/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/it/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/it/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ur/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ur/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/de/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/de/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/my/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/my/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ru/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ru/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/id/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/id/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/vi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/vi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/az/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/az/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/et/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/et/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/io/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/io/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gd/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gd/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/uk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/uk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/te/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/te/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/el/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/el/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/km/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/km/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eo/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eo/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/be/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/be/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/locale/be/LC_MESSAGES copying build/lib/django/contrib/flatpages/sitemaps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages copying build/lib/django/contrib/flatpages/admin.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/api.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/views.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/context_processors.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/test.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages copying build/lib/django/contrib/messages/constants.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/cookie.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/fallback.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/session.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage copying build/lib/django/contrib/messages/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize copying build/lib/django/contrib/humanize/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/templatetags copying build/lib/django/contrib/humanize/templatetags/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/templatetags copying build/lib/django/contrib/humanize/templatetags/humanize.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/templatetags copying build/lib/django/contrib/humanize/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sw/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sw/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ia/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ia/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ne/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ne/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/af/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/af/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ja/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ja/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/os/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/os/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/th/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/th/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sq/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sq/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/he/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/he/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/is/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/is/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ka/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ka/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ro/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ro/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ky/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ky/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ta/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ta/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/udm/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/udm/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ast/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ast/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/da/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/da/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ml/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ml/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ms/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ms/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uz/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uz/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ga/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ga/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ko/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ko/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ug/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ug/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/br/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/br/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ca/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ca/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/it/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/it/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ur/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ur/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/de/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/de/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/my/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/my/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ru/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ru/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/id/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/id/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/vi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/vi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/az/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/az/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/et/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/et/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/io/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/io/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gd/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gd/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/te/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/te/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/el/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/el/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/km/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/km/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eo/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eo/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/be/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/be/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/locale/be/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects copying build/lib/django/contrib/redirects/middleware.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects copying build/lib/django/contrib/redirects/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects copying build/lib/django/contrib/redirects/apps.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sw/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sw/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ia/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ia/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ne/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ne/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/af/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/af/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ja/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ja/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ja/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/os/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/os/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/th/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/th/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/th/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sq/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sq/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sq/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/he/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/he/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/he/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/is/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/is/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/is/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ka/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ka/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ka/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ro/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ro/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ro/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ky/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ky/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ky/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ta/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ta/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ta/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/udm/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/udm/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ast/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ast/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/da/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/da/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/da/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ml/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ml/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ml/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_AU/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ms/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ms/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ms/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uz/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uz/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uz/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ar/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ga/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ga/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ga/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ko/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ko/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ko/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ug/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ug/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ug/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/br/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/br/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ca/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ca/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ca/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/nn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/it/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/it/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ur/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ur/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ckb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_CO/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/de/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/de/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/tk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/my/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/my/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ru/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ru/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/id/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/id/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/id/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kab/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kab/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/vi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/vi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/vi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/az/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/az/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/az/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/et/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/et/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/et/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fi/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/io/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/io/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/fa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bg/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/bs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/mk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gd/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gd/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/gd/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/te/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/te/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/te/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/el/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/el/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/km/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/km/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/km/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eo/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eo/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/eo/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/be/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/be/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/locale/be/LC_MESSAGES copying build/lib/django/contrib/redirects/admin.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/signals.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/query_utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/manager.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/expressions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/where.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/datastructures.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/constants.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/compiler.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/query.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/sql/subqueries.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql copying build/lib/django/db/models/constraints.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/lookups.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/enums.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/window.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/mixins.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/datetime.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/math.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/comparison.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/functions/text.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions copying build/lib/django/db/models/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/aggregates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/constants.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/json.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/mixins.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/related.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/related_descriptors.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/reverse_related.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/proxy.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/files.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/related_lookups.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/fields/generated.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields copying build/lib/django/db/models/query.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/indexes.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/options.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/deletion.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/models/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models copying build/lib/django/db/transaction.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends copying build/lib/django/db/backends/signals.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/functions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/validation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/creation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/oracledb_any.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/oracle/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle copying build/lib/django/db/backends/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/_functions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/creation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/validation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/creation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/base/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base copying build/lib/django/db/backends/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends copying build/lib/django/db/backends/ddl_references.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/validation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/creation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/compiler.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql copying build/lib/django/db/backends/mysql/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/schema.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/operations.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/creation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/psycopg_any.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/introspection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy copying build/lib/django/db/backends/dummy/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy copying build/lib/django/db/backends/dummy/features.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy copying build/lib/django/db/backends/dummy/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/state.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/graph.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/migration.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/loader.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/questioner.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/exceptions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/optimizer.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/writer.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations copying build/lib/django/db/migrations/operations/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations copying build/lib/django/db/migrations/operations/fields.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations copying build/lib/django/db/migrations/operations/special.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations copying build/lib/django/db/migrations/operations/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations copying build/lib/django/db/migrations/operations/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations copying build/lib/django/db/migrations/autodetector.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/recorder.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/executor.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/migrations/serializer.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations copying build/lib/django/db/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db copying build/lib/django/db/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db copying build/lib/django/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/signals.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/client.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/html.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/testcases.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/selenium.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/runner.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test copying build/lib/django/test/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/generic/detail.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/generic/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/generic/list.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/generic/edit.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/generic/dates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/generic/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic copying build/lib/django/views/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/csrf_403.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/directory_index.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/technical_500.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/technical_500.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/i18n_catalog.js -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/technical_404.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/templates/default_urlconf.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/templates copying build/lib/django/views/debug.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views copying build/lib/django/views/static.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/clickjacking.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/http.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/gzip.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/debug.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/common.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/csrf.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/cache.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/decorators/vary.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators copying build/lib/django/views/defaults.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views copying build/lib/django/views/csrf.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views copying build/lib/django/views/i18n.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/loader_tags.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/autoreload.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/library.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/backends/django.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/backends/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/backends/dummy.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/backends/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/backends/jinja2.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/backends/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends copying build/lib/django/template/context.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loaders/cached.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loaders/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loaders/app_directories.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loaders/locmem.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loaders/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loaders/filesystem.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders copying build/lib/django/template/loader.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/smartif.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/defaultfilters.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/exceptions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/engine.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/context_processors.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/defaulttags.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/response.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template copying build/lib/django/template/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags copying build/lib/django/templatetags/l10n.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags copying build/lib/django/templatetags/tz.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags copying build/lib/django/templatetags/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags copying build/lib/django/templatetags/static.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags copying build/lib/django/templatetags/cache.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags copying build/lib/django/templatetags/i18n.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/forms.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/fields.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/p.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/list copying build/lib/django/forms/templates/django/forms/errors/list/text.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/list copying build/lib/django/forms/templates/django/forms/errors/list/default.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/list copying build/lib/django/forms/templates/django/forms/errors/list/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/list creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/errors/dict/text.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/errors/dict/default.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/errors/dict/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/field.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/label.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/select.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/text.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/password.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/url.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/date.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/time.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/file.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/number.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/email.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/table.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/p.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/table.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/div.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/div.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/attrs.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/templates/django/forms copying build/lib/django/forms/formsets.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/renderers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/models.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2 creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/p.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/list copying build/lib/django/forms/jinja2/django/forms/errors/list/text.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/list copying build/lib/django/forms/jinja2/django/forms/errors/list/default.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/list copying build/lib/django/forms/jinja2/django/forms/errors/list/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/list creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/errors/dict/text.txt -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/errors/dict/default.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/errors/dict/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/field.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/label.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/table.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/p.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/table.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/div.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/ul.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/div.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/attrs.html -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/jinja2/django/forms copying build/lib/django/forms/widgets.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms copying build/lib/django/forms/boundfield.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/clickjacking.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/http.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/gzip.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/common.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/csrf.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/locale.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/cache.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware copying build/lib/django/middleware/security.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http copying build/lib/django/http/multipartparser.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http copying build/lib/django/http/cookie.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http copying build/lib/django/http/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http copying build/lib/django/http/request.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http copying build/lib/django/http/response.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http copying build/lib/django/__main__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template copying build/lib/django/conf/app_template/models.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template copying build/lib/django/conf/app_template/apps.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template copying build/lib/django/conf/app_template/__init__.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template/migrations copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template/migrations copying build/lib/django/conf/app_template/tests.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template copying build/lib/django/conf/app_template/admin.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template copying build/lib/django/conf/app_template/views.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/app_template creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template copying build/lib/django/conf/project_template/manage.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/project_name copying build/lib/django/conf/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf copying build/lib/django/conf/global_settings.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls copying build/lib/django/conf/urls/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls copying build/lib/django/conf/urls/static.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls copying build/lib/django/conf/urls/i18n.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sw creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sw/LC_MESSAGES copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sw/LC_MESSAGES copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sw/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ia creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ia/LC_MESSAGES copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ia/LC_MESSAGES copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ia/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tt/LC_MESSAGES copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tt/LC_MESSAGES copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CH copying build/lib/django/conf/locale/fr_CH/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CH copying build/lib/django/conf/locale/fr_CH/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CH creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn/LC_MESSAGES copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn/LC_MESSAGES copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn/LC_MESSAGES copying build/lib/django/conf/locale/kn/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn copying build/lib/django/conf/locale/kn/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_IE copying build/lib/django/conf/locale/en_IE/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_IE copying build/lib/django/conf/locale/en_IE/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_IE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ne creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ne/LC_MESSAGES copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ne/LC_MESSAGES copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ne/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/af creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/af/LC_MESSAGES copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/af/LC_MESSAGES copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/af/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja/LC_MESSAGES copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja/LC_MESSAGES copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja/LC_MESSAGES copying build/lib/django/conf/locale/ja/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja copying build/lib/django/conf/locale/ja/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt/LC_MESSAGES copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt/LC_MESSAGES copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt/LC_MESSAGES copying build/lib/django/conf/locale/pt/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt copying build/lib/django/conf/locale/pt/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/os creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/os/LC_MESSAGES copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/os/LC_MESSAGES copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/os/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th/LC_MESSAGES copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th/LC_MESSAGES copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th/LC_MESSAGES copying build/lib/django/conf/locale/th/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th copying build/lib/django/conf/locale/th/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk/LC_MESSAGES copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk/LC_MESSAGES copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk/LC_MESSAGES copying build/lib/django/conf/locale/sk/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk copying build/lib/django/conf/locale/sk/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq/LC_MESSAGES copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq/LC_MESSAGES copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq/LC_MESSAGES copying build/lib/django/conf/locale/sq/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq copying build/lib/django/conf/locale/sq/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he/LC_MESSAGES copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he/LC_MESSAGES copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he/LC_MESSAGES copying build/lib/django/conf/locale/he/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he copying build/lib/django/conf/locale/he/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_BE copying build/lib/django/conf/locale/fr_BE/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_BE copying build/lib/django/conf/locale/fr_BE/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_BE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is/LC_MESSAGES copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is/LC_MESSAGES copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is/LC_MESSAGES copying build/lib/django/conf/locale/is/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is copying build/lib/django/conf/locale/is/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka/LC_MESSAGES copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka/LC_MESSAGES copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka/LC_MESSAGES copying build/lib/django/conf/locale/ka/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka copying build/lib/django/conf/locale/ka/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro/LC_MESSAGES copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro/LC_MESSAGES copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro/LC_MESSAGES copying build/lib/django/conf/locale/ro/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro copying build/lib/django/conf/locale/ro/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky/LC_MESSAGES copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky/LC_MESSAGES copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky/LC_MESSAGES copying build/lib/django/conf/locale/ky/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky copying build/lib/django/conf/locale/ky/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr/LC_MESSAGES copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr/LC_MESSAGES copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr/LC_MESSAGES copying build/lib/django/conf/locale/tr/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr copying build/lib/django/conf/locale/tr/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr/LC_MESSAGES copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr/LC_MESSAGES copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr/LC_MESSAGES copying build/lib/django/conf/locale/fr/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr copying build/lib/django/conf/locale/fr/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ/LC_MESSAGES copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ/LC_MESSAGES copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ/LC_MESSAGES copying build/lib/django/conf/locale/ar_DZ/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ copying build/lib/django/conf/locale/ar_DZ/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mr/LC_MESSAGES copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mr/LC_MESSAGES copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta/LC_MESSAGES copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta/LC_MESSAGES copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta/LC_MESSAGES copying build/lib/django/conf/locale/ta/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta copying build/lib/django/conf/locale/ta/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta copying build/lib/django/conf/locale/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/udm creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/udm/LC_MESSAGES copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/udm/LC_MESSAGES copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/udm/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy/LC_MESSAGES copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy/LC_MESSAGES copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy/LC_MESSAGES copying build/lib/django/conf/locale/fy/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy copying build/lib/django/conf/locale/fy/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ast creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ast/LC_MESSAGES copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ast/LC_MESSAGES copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ast/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da/LC_MESSAGES copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da/LC_MESSAGES copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da/LC_MESSAGES copying build/lib/django/conf/locale/da/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da copying build/lib/django/conf/locale/da/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb/LC_MESSAGES copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb/LC_MESSAGES copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb/LC_MESSAGES copying build/lib/django/conf/locale/nb/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb copying build/lib/django/conf/locale/nb/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_VE creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_VE/LC_MESSAGES copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_VE/LC_MESSAGES copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_VE/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hant/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant copying build/lib/django/conf/locale/zh_Hant/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy/LC_MESSAGES copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy/LC_MESSAGES copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy/LC_MESSAGES copying build/lib/django/conf/locale/cy/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy copying build/lib/django/conf/locale/cy/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml/LC_MESSAGES copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml/LC_MESSAGES copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml/LC_MESSAGES copying build/lib/django/conf/locale/ml/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml copying build/lib/django/conf/locale/ml/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hsb/LC_MESSAGES copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hsb/LC_MESSAGES copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kk/LC_MESSAGES copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kk/LC_MESSAGES copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU/LC_MESSAGES copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU/LC_MESSAGES copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU/LC_MESSAGES copying build/lib/django/conf/locale/en_AU/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU copying build/lib/django/conf/locale/en_AU/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms/LC_MESSAGES copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms/LC_MESSAGES copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms/LC_MESSAGES copying build/lib/django/conf/locale/ms/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms copying build/lib/django/conf/locale/ms/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl/LC_MESSAGES copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl/LC_MESSAGES copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl/LC_MESSAGES copying build/lib/django/conf/locale/nl/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl copying build/lib/django/conf/locale/nl/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz/LC_MESSAGES copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz/LC_MESSAGES copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz/LC_MESSAGES copying build/lib/django/conf/locale/uz/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz copying build/lib/django/conf/locale/uz/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar/LC_MESSAGES copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar/LC_MESSAGES copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar/LC_MESSAGES copying build/lib/django/conf/locale/ar/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar copying build/lib/django/conf/locale/ar/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga/LC_MESSAGES copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga/LC_MESSAGES copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga/LC_MESSAGES copying build/lib/django/conf/locale/ga/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga copying build/lib/django/conf/locale/ga/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko/LC_MESSAGES copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko/LC_MESSAGES copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko/LC_MESSAGES copying build/lib/django/conf/locale/ko/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko copying build/lib/django/conf/locale/ko/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug/LC_MESSAGES copying build/lib/django/conf/locale/ug/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug/LC_MESSAGES copying build/lib/django/conf/locale/ug/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug/LC_MESSAGES copying build/lib/django/conf/locale/ug/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug copying build/lib/django/conf/locale/ug/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu/LC_MESSAGES copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu/LC_MESSAGES copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu/LC_MESSAGES copying build/lib/django/conf/locale/hu/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu copying build/lib/django/conf/locale/hu/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/br creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/br/LC_MESSAGES copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/br/LC_MESSAGES copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/br/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca/LC_MESSAGES copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca/LC_MESSAGES copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca/LC_MESSAGES copying build/lib/django/conf/locale/ca/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca copying build/lib/django/conf/locale/ca/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv/LC_MESSAGES copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv/LC_MESSAGES copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv/LC_MESSAGES copying build/lib/django/conf/locale/sv/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv copying build/lib/django/conf/locale/sv/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi/LC_MESSAGES copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi/LC_MESSAGES copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi/LC_MESSAGES copying build/lib/django/conf/locale/hi/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi copying build/lib/django/conf/locale/hi/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn/LC_MESSAGES copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn/LC_MESSAGES copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn/LC_MESSAGES copying build/lib/django/conf/locale/nn/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn copying build/lib/django/conf/locale/nn/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it/LC_MESSAGES copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it/LC_MESSAGES copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it/LC_MESSAGES copying build/lib/django/conf/locale/it/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it copying build/lib/django/conf/locale/it/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg/LC_MESSAGES copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg/LC_MESSAGES copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg/LC_MESSAGES copying build/lib/django/conf/locale/tg/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg copying build/lib/django/conf/locale/tg/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ur creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ur/LC_MESSAGES copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ur/LC_MESSAGES copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ur/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb/LC_MESSAGES copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb/LC_MESSAGES copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb/LC_MESSAGES copying build/lib/django/conf/locale/ckb/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb copying build/lib/django/conf/locale/ckb/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO/LC_MESSAGES copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO/LC_MESSAGES copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO/LC_MESSAGES copying build/lib/django/conf/locale/es_CO/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO copying build/lib/django/conf/locale/es_CO/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr/LC_MESSAGES copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr/LC_MESSAGES copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr/LC_MESSAGES copying build/lib/django/conf/locale/sr/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr copying build/lib/django/conf/locale/sr/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de/LC_MESSAGES copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de/LC_MESSAGES copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de/LC_MESSAGES copying build/lib/django/conf/locale/de/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de copying build/lib/django/conf/locale/de/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn/LC_MESSAGES copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn/LC_MESSAGES copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn/LC_MESSAGES copying build/lib/django/conf/locale/mn/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn copying build/lib/django/conf/locale/mn/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl/LC_MESSAGES copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl/LC_MESSAGES copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl/LC_MESSAGES copying build/lib/django/conf/locale/gl/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl copying build/lib/django/conf/locale/gl/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de_CH copying build/lib/django/conf/locale/de_CH/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de_CH copying build/lib/django/conf/locale/de_CH/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de_CH creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk/LC_MESSAGES copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk/LC_MESSAGES copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk/LC_MESSAGES copying build/lib/django/conf/locale/tk/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk copying build/lib/django/conf/locale/tk/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr/LC_MESSAGES copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr/LC_MESSAGES copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr/LC_MESSAGES copying build/lib/django/conf/locale/hr/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr copying build/lib/django/conf/locale/hr/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv/LC_MESSAGES copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv/LC_MESSAGES copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv/LC_MESSAGES copying build/lib/django/conf/locale/lv/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv copying build/lib/django/conf/locale/lv/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en/LC_MESSAGES copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en/LC_MESSAGES copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en/LC_MESSAGES copying build/lib/django/conf/locale/en/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en copying build/lib/django/conf/locale/en/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig/LC_MESSAGES copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig/LC_MESSAGES copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig/LC_MESSAGES copying build/lib/django/conf/locale/ig/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig copying build/lib/django/conf/locale/ig/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hy creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hy/LC_MESSAGES copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hy/LC_MESSAGES copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hy/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu/LC_MESSAGES copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu/LC_MESSAGES copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu/LC_MESSAGES copying build/lib/django/conf/locale/eu/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu copying build/lib/django/conf/locale/eu/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_NI copying build/lib/django/conf/locale/es_NI/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_NI copying build/lib/django/conf/locale/es_NI/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_NI creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/my creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/my/LC_MESSAGES copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/my/LC_MESSAGES copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/my/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl/LC_MESSAGES copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl/LC_MESSAGES copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl/LC_MESSAGES copying build/lib/django/conf/locale/pl/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl copying build/lib/django/conf/locale/pl/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru/LC_MESSAGES copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru/LC_MESSAGES copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru/LC_MESSAGES copying build/lib/django/conf/locale/ru/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru copying build/lib/django/conf/locale/ru/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id/LC_MESSAGES copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id/LC_MESSAGES copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id/LC_MESSAGES copying build/lib/django/conf/locale/id/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id copying build/lib/django/conf/locale/id/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kab creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kab/LC_MESSAGES copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kab/LC_MESSAGES copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kab/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn/LC_MESSAGES copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn/LC_MESSAGES copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn/LC_MESSAGES copying build/lib/django/conf/locale/bn/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn copying build/lib/django/conf/locale/bn/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lb/LC_MESSAGES copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lb/LC_MESSAGES copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi/LC_MESSAGES copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi/LC_MESSAGES copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi/LC_MESSAGES copying build/lib/django/conf/locale/vi/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi copying build/lib/django/conf/locale/vi/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az/LC_MESSAGES copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az/LC_MESSAGES copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az/LC_MESSAGES copying build/lib/django/conf/locale/az/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az copying build/lib/django/conf/locale/az/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR/LC_MESSAGES copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR/LC_MESSAGES copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR/LC_MESSAGES copying build/lib/django/conf/locale/pt_BR/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR copying build/lib/django/conf/locale/pt_BR/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et/LC_MESSAGES copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et/LC_MESSAGES copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et/LC_MESSAGES copying build/lib/django/conf/locale/et/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et copying build/lib/django/conf/locale/et/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs/LC_MESSAGES copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs/LC_MESSAGES copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs/LC_MESSAGES copying build/lib/django/conf/locale/cs/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs copying build/lib/django/conf/locale/cs/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi/LC_MESSAGES copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi/LC_MESSAGES copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi/LC_MESSAGES copying build/lib/django/conf/locale/fi/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi copying build/lib/django/conf/locale/fi/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es/LC_MESSAGES copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es/LC_MESSAGES copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es/LC_MESSAGES copying build/lib/django/conf/locale/es/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es copying build/lib/django/conf/locale/es/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/io creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/io/LC_MESSAGES copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/io/LC_MESSAGES copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/io/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa/LC_MESSAGES copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa/LC_MESSAGES copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa/LC_MESSAGES copying build/lib/django/conf/locale/fa/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa copying build/lib/django/conf/locale/fa/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg/LC_MESSAGES copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg/LC_MESSAGES copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg/LC_MESSAGES copying build/lib/django/conf/locale/bg/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg copying build/lib/django/conf/locale/bg/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs/LC_MESSAGES copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs/LC_MESSAGES copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs/LC_MESSAGES copying build/lib/django/conf/locale/bs/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs copying build/lib/django/conf/locale/bs/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl/LC_MESSAGES copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl/LC_MESSAGES copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl/LC_MESSAGES copying build/lib/django/conf/locale/sl/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl copying build/lib/django/conf/locale/sl/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX/LC_MESSAGES copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX/LC_MESSAGES copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX/LC_MESSAGES copying build/lib/django/conf/locale/es_MX/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX copying build/lib/django/conf/locale/es_MX/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk/LC_MESSAGES copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk/LC_MESSAGES copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk/LC_MESSAGES copying build/lib/django/conf/locale/mk/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk copying build/lib/django/conf/locale/mk/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd/LC_MESSAGES copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd/LC_MESSAGES copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd/LC_MESSAGES copying build/lib/django/conf/locale/gd/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd copying build/lib/django/conf/locale/gd/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk/LC_MESSAGES copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk/LC_MESSAGES copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk/LC_MESSAGES copying build/lib/django/conf/locale/uk/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk copying build/lib/django/conf/locale/uk/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt/LC_MESSAGES copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt/LC_MESSAGES copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt/LC_MESSAGES copying build/lib/django/conf/locale/lt/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt copying build/lib/django/conf/locale/lt/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pa creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pa/LC_MESSAGES copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pa/LC_MESSAGES copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pa/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te/LC_MESSAGES copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te/LC_MESSAGES copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te/LC_MESSAGES copying build/lib/django/conf/locale/te/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te copying build/lib/django/conf/locale/te/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/dsb creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/dsb/LC_MESSAGES copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/dsb/LC_MESSAGES copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/dsb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB/LC_MESSAGES copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB/LC_MESSAGES copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB/LC_MESSAGES copying build/lib/django/conf/locale/en_GB/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB copying build/lib/django/conf/locale/en_GB/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/django/conf/locale/sr_Latn/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn copying build/lib/django/conf/locale/sr_Latn/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el/LC_MESSAGES copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el/LC_MESSAGES copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el/LC_MESSAGES copying build/lib/django/conf/locale/el/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el copying build/lib/django/conf/locale/el/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR/LC_MESSAGES copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR/LC_MESSAGES copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR/LC_MESSAGES copying build/lib/django/conf/locale/es_AR/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR copying build/lib/django/conf/locale/es_AR/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_PR copying build/lib/django/conf/locale/es_PR/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_PR copying build/lib/django/conf/locale/es_PR/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_PR creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km/LC_MESSAGES copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km/LC_MESSAGES copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km/LC_MESSAGES copying build/lib/django/conf/locale/km/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km copying build/lib/django/conf/locale/km/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CA copying build/lib/django/conf/locale/fr_CA/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CA copying build/lib/django/conf/locale/fr_CA/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CA creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo/LC_MESSAGES copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo/LC_MESSAGES copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo/LC_MESSAGES copying build/lib/django/conf/locale/eo/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo copying build/lib/django/conf/locale/eo/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hans/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans copying build/lib/django/conf/locale/zh_Hans/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/be creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/be/LC_MESSAGES copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/be/LC_MESSAGES copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/be/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/resolvers.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/exceptions.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/utils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/conf.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/converters.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls copying build/lib/django/urls/base.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/jslex.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/xmlutils.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/crypto.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/asyncio.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/autoreload.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/version.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/archive.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils creating /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation copying build/lib/django/utils/translation/trans_real.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation copying build/lib/django/utils/translation/reloader.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation copying build/lib/django/utils/translation/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation copying build/lib/django/utils/translation/template.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation copying build/lib/django/utils/translation/trans_null.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation copying build/lib/django/utils/tree.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/feedgenerator.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/connection.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/deconstruct.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/hashable.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/_os.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/timezone.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/numberformat.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/choices.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/log.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/inspect.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/__init__.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/datastructures.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/http.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/html.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/deprecation.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/timesince.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/functional.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/ipv6.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/regex_helper.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/duration.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/formats.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/termcolors.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/dateformat.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/safestring.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/decorators.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/lorem_ipsum.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/text.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/itercompat.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/encoding.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/dates.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/cache.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/dateparse.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils copying build/lib/django/utils/module_loading.py -> /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/signals.py to signals.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/signing.py to signing.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/console.py to console.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/smtp.py to smtp.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/dummy.py to dummy.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/filebased.py to filebased.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/locmem.py to locmem.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/backends/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/message.py to message.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/mail/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/paginator.py to paginator.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/redis.py to redis.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/dummy.py to dummy.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/db.py to db.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/memcached.py to memcached.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/filebased.py to filebased.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/locmem.py to locmem.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/backends/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/cache/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers/exception.py to exception.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers/asgi.py to asgi.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers/wsgi.py to wsgi.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/handlers/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/sql.py to sql.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/color.py to color.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/templates.py to templates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/optimizemigration.py to optimizemigration.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/flush.py to flush.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/compilemessages.py to compilemessages.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/showmigrations.py to showmigrations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/testserver.py to testserver.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/dumpdata.py to dumpdata.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/sendtestemail.py to sendtestemail.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/inspectdb.py to inspectdb.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/loaddata.py to loaddata.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/migrate.py to migrate.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/makemessages.py to makemessages.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/sqlflush.py to sqlflush.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/sqlmigrate.py to sqlmigrate.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/test.py to test.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/squashmigrations.py to squashmigrations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/startproject.py to startproject.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/diffsettings.py to diffsettings.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/runserver.py to runserver.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/createcachetable.py to createcachetable.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/startapp.py to startapp.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/dbshell.py to dbshell.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/sqlsequencereset.py to sqlsequencereset.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/shell.py to shell.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/check.py to check.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/commands/makemigrations.py to makemigrations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/management/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/validators.py to validators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/move.py to move.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/temp.py to temp.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/images.py to images.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/uploadhandler.py to uploadhandler.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/uploadedfile.py to uploadedfile.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage/mixins.py to mixins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage/handler.py to handler.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage/memory.py to memory.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/storage/filesystem.py to filesystem.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/locks.py to locks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/files/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/asgi.py to asgi.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/json.py to json.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/xml_serializer.py to xml_serializer.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/python.py to python.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/pyyaml.py to pyyaml.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/jsonl.py to jsonl.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/serializers/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/wsgi.py to wsgi.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/messages.py to messages.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/translation.py to translation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/model_checks.py to model_checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/templates.py to templates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/urls.py to urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security/sessions.py to sessions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security/csrf.py to csrf.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/security/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/database.py to database.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/async_checks.py to async_checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/files.py to files.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/registry.py to registry.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/caches.py to caches.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/compatibility/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/checks/compatibility/django_4_0.py to django_4_0.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/servers/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/core/servers/basehttp.py to basehttp.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/dispatch/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/dispatch/dispatcher.py to dispatcher.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/shortcuts.py to shortcuts.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps/config.py to config.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/apps/registry.py to registry.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/syndication/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/checks.py to checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/shortcuts.py to shortcuts.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/migrations/0002_alter_domain_unique.py to 0002_alter_domain_unique.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/managers.py to managers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/requests.py to requests.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/management.py to management.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sites/admin.py to admin.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/functions.py to functions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/signals.py to signals.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/serializers.py to serializers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/expressions.py to expressions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates/mixins.py to mixins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates/statistics.py to statistics.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/aggregates/general.py to general.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/constraints.py to constraints.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/lookups.py to lookups.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/search.py to search.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/validators.py to validators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms/ranges.py to ranges.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms/array.py to array.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/forms/hstore.py to hstore.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/ranges.py to ranges.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/array.py to array.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/citext.py to citext.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/hstore.py to hstore.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/fields/jsonb.py to jsonb.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/indexes.py to indexes.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/postgres/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/srs.py to srs.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/libgdal.py to libgdal.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/srs.py to srs.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/generation.py to generation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/geom.py to geom.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/raster.py to raster.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/ds.py to ds.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/prototypes/errcheck.py to errcheck.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/driver.py to driver.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/error.py to error.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster/band.py to band.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster/source.py to source.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster/const.py to const.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/raster/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/feature.py to feature.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/datasource.py to datasource.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/geomtype.py to geomtype.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/envelope.py to envelope.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/layer.py to layer.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/geometries.py to geometries.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/field.py to field.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/gdal/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/shortcuts.py to shortcuts.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geometry.py to geometry.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/measure.py to measure.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/geometry.py to geometry.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/linestring.py to linestring.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/topology.py to topology.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/geom.py to geom.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/prepared.py to prepared.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/errcheck.py to errcheck.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/io.py to io.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/predicates.py to predicates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/threadsafe.py to threadsafe.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/misc.py to misc.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prototypes/coordseq.py to coordseq.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/libgeos.py to libgeos.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/error.py to error.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/prepared.py to prepared.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/io.py to io.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/polygon.py to polygon.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/collections.py to collections.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/point.py to point.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/factory.py to factory.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/mutable_list.py to mutable_list.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/coordseq.py to coordseq.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geos/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/admin/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/admin/options.py to options.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/functions.py to functions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/sql/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/sql/conversion.py to conversion.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/fields.py to fields.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/lookups.py to lookups.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/proxy.py to proxy.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/models/aggregates.py to aggregates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/adapter.py to adapter.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/oracle/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base/adapter.py to adapter.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/base/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/mysql/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/adapter.py to adapter.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/pgraster.py to pgraster.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/const.py to const.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/postgis/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/adapter.py to adapter.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/backends/spatialite/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/db/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/feeds.py to feeds.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands/inspectdb.py to inspectdb.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/commands/ogrinspect.py to ogrinspect.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps/kml.py to kml.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/sitemaps/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms/fields.py to fields.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/forms/widgets.py to widgets.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/serializers/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/serializers/geojson.py to geojson.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2/resources.py to resources.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/geoip2/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils/srs.py to srs.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils/ogrinfo.py to ogrinfo.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils/layermapping.py to layermapping.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/utils/ogrinspect.py to ogrinspect.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/gis/ptr.py to ptr.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/checks.py to checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/sites.py to sites.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py to 0002_logentry_remove_auto_add.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py to 0003_logentry_add_action_flag_choices.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/forms.py to forms.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/filters.py to filters.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views/main.py to main.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views/autocomplete.py to autocomplete.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/views/decorators.py to decorators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags/admin_urls.py to admin_urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags/log.py to log.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags/admin_list.py to admin_list.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags/admin_modify.py to admin_modify.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/templatetags/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/tests.py to tests.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/helpers.py to helpers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/actions.py to actions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/decorators.py to decorators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/widgets.py to widgets.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admin/options.py to options.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sitemaps/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/urls.py to urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/admindocs/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/checks.py to checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/password_validation.py to password_validation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/signals.py to signals.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/mixins.py to mixins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0006_require_contenttypes_0002.py to 0006_require_contenttypes_0002.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py to 0009_alter_user_last_name_max_length.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0010_alter_group_name_max_length.py to 0010_alter_group_name_max_length.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0003_alter_user_email_max_length.py to 0003_alter_user_email_max_length.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0005_alter_user_last_login_null.py to 0005_alter_user_last_login_null.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0008_alter_user_username_max_length.py to 0008_alter_user_username_max_length.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0011_update_proxy_permissions.py to 0011_update_proxy_permissions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py to 0012_alter_user_first_name_max_length.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0004_alter_user_username_opts.py to 0004_alter_user_username_opts.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py to 0007_alter_validators_add_error_messages.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py to 0002_alter_permission_name_max_length.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/urls.py to urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/tokens.py to tokens.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/forms.py to forms.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/base_user.py to base_user.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/handlers/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/handlers/modwsgi.py to modwsgi.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands/createsuperuser.py to createsuperuser.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/commands/changepassword.py to changepassword.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/validators.py to validators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/context_processors.py to context_processors.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/decorators.py to decorators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/hashers.py to hashers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/auth/admin.py to admin.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/serializers.py to serializers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/signed_cookies.py to signed_cookies.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/cached_db.py to cached_db.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/db.py to db.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/file.py to file.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/cache.py to cache.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/backends/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management/commands/clearsessions.py to clearsessions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/base_session.py to base_session.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/sessions/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/checks.py to checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/urls.py to urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py to collectstatic.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands/runserver.py to runserver.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/commands/findstatic.py to findstatic.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/handlers.py to handlers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/testing.py to testing.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/finders.py to finders.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/storage.py to storage.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/staticfiles/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/checks.py to checks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py to 0002_remove_content_type_name.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/forms.py to forms.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/fields.py to fields.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py to remove_stale_contenttypes.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/prefetch.py to prefetch.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/contenttypes/admin.py to admin.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/urls.py to urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/forms.py to forms.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/templatetags/flatpages.py to flatpages.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/sitemaps.py to sitemaps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/flatpages/admin.py to admin.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/api.py to api.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/views.py to views.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/context_processors.py to context_processors.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/test.py to test.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/constants.py to constants.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage/cookie.py to cookie.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage/fallback.py to fallback.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage/session.py to session.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/storage/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/messages/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/templatetags/humanize.py to humanize.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/humanize/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py to 0002_alter_redirect_new_path_help_text.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/middleware.py to middleware.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/contrib/redirects/admin.py to admin.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/signals.py to signals.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/query_utils.py to query_utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/manager.py to manager.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/expressions.py to expressions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/where.py to where.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/datastructures.py to datastructures.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/constants.py to constants.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/compiler.py to compiler.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/query.py to query.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/sql/subqueries.py to subqueries.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/constraints.py to constraints.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/lookups.py to lookups.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/enums.py to enums.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/window.py to window.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/mixins.py to mixins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/datetime.py to datetime.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/math.py to math.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/comparison.py to comparison.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/functions/text.py to text.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/aggregates.py to aggregates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/constants.py to constants.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/json.py to json.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/mixins.py to mixins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/related.py to related.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/related_descriptors.py to related_descriptors.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/reverse_related.py to reverse_related.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/proxy.py to proxy.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/files.py to files.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/related_lookups.py to related_lookups.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/fields/generated.py to generated.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/query.py to query.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/indexes.py to indexes.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/options.py to options.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/deletion.py to deletion.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/models/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/transaction.py to transaction.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/signals.py to signals.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/functions.py to functions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/validation.py to validation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/creation.py to creation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/oracledb_any.py to oracledb_any.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/oracle/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/_functions.py to _functions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/creation.py to creation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/sqlite3/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/validation.py to validation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/creation.py to creation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/base/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/ddl_references.py to ddl_references.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/validation.py to validation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/creation.py to creation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/compiler.py to compiler.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/mysql/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/schema.py to schema.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/operations.py to operations.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/creation.py to creation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/psycopg_any.py to psycopg_any.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/introspection.py to introspection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/postgresql/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy/features.py to features.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/backends/dummy/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/state.py to state.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/graph.py to graph.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/migration.py to migration.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/loader.py to loader.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/questioner.py to questioner.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/optimizer.py to optimizer.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/writer.py to writer.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations/fields.py to fields.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations/special.py to special.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/operations/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/autodetector.py to autodetector.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/recorder.py to recorder.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/executor.py to executor.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/migrations/serializer.py to serializer.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/db/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/signals.py to signals.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/client.py to client.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/html.py to html.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/testcases.py to testcases.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/selenium.py to selenium.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/runner.py to runner.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/test/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic/detail.py to detail.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic/list.py to list.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic/edit.py to edit.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic/dates.py to dates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/generic/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/debug.py to debug.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/static.py to static.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/clickjacking.py to clickjacking.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/http.py to http.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/gzip.py to gzip.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/debug.py to debug.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/common.py to common.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/csrf.py to csrf.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/cache.py to cache.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/decorators/vary.py to vary.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/defaults.py to defaults.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/csrf.py to csrf.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/views/i18n.py to i18n.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loader_tags.py to loader_tags.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/autoreload.py to autoreload.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/library.py to library.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends/django.py to django.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends/dummy.py to dummy.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends/jinja2.py to jinja2.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/backends/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/context.py to context.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders/cached.py to cached.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders/app_directories.py to app_directories.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders/locmem.py to locmem.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loaders/filesystem.py to filesystem.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/loader.py to loader.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/smartif.py to smartif.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/defaultfilters.py to defaultfilters.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/engine.py to engine.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/context_processors.py to context_processors.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/defaulttags.py to defaulttags.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/response.py to response.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/template/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags/l10n.py to l10n.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags/tz.py to tz.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags/static.py to static.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags/cache.py to cache.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/templatetags/i18n.py to i18n.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/forms.py to forms.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/fields.py to fields.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/formsets.py to formsets.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/renderers.py to renderers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/widgets.py to widgets.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/forms/boundfield.py to boundfield.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/clickjacking.py to clickjacking.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/http.py to http.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/gzip.py to gzip.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/common.py to common.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/csrf.py to csrf.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/locale.py to locale.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/cache.py to cache.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/middleware/security.py to security.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http/multipartparser.py to multipartparser.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http/cookie.py to cookie.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http/request.py to request.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/http/response.py to response.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/__main__.py to __main__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/global_settings.py to global_settings.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls/static.py to static.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/urls/i18n.py to i18n.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CH/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CH/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/kn/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_IE/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_IE/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ja/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/th/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sk/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sq/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/he/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_BE/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_BE/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/is/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ka/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ro/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ky/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tr/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar_DZ/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ta/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fy/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/da/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nb/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hant/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cy/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ml/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_AU/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ms/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nl/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uz/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ar/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ga/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ko/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ug/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hu/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ca/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sv/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hi/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/nn/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/it/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tg/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ckb/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_CO/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mn/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gl/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de_CH/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/de_CH/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/tk/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/hr/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lv/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ig/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eu/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_NI/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_NI/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pl/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/ru/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/id/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bn/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/vi/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/az/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/pt_BR/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/et/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/cs/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fi/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fa/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bg/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/bs/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sl/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_MX/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/mk/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/gd/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/uk/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/lt/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/te/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/en_GB/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/sr_Latn/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/el/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_AR/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_PR/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/es_PR/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/km/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CA/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/fr_CA/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/eo/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/locale/zh_Hans/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/resolvers.py to resolvers.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/utils.py to utils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/conf.py to conf.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/converters.py to converters.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/urls/base.py to base.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/jslex.py to jslex.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/xmlutils.py to xmlutils.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/crypto.py to crypto.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/asyncio.py to asyncio.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/autoreload.py to autoreload.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/version.py to version.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/archive.py to archive.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation/trans_real.py to trans_real.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation/reloader.py to reloader.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation/template.py to template.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/translation/trans_null.py to trans_null.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/tree.py to tree.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/feedgenerator.py to feedgenerator.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/connection.py to connection.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/deconstruct.py to deconstruct.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/hashable.py to hashable.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/_os.py to _os.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/timezone.py to timezone.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/numberformat.py to numberformat.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/choices.py to choices.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/log.py to log.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/inspect.py to inspect.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/datastructures.py to datastructures.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/http.py to http.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/html.py to html.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/deprecation.py to deprecation.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/timesince.py to timesince.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/functional.py to functional.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/ipv6.py to ipv6.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/regex_helper.py to regex_helper.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/duration.py to duration.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/formats.py to formats.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/termcolors.py to termcolors.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/dateformat.py to dateformat.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/safestring.py to safestring.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/decorators.py to decorators.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/lorem_ipsum.py to lorem_ipsum.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/text.py to text.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/itercompat.py to itercompat.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/encoding.py to encoding.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/dates.py to dates.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/cache.py to cache.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/dateparse.py to dateparse.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/utils/module_loading.py to module_loading.cpython-311.pyc writing byte-compilation script '/tmp/tmpzy6_g3nd.py' /usr/bin/python3 /tmp/tmpzy6_g3nd.py removing /tmp/tmpzy6_g3nd.py running install_egg_info 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' Copying Django.egg-info to /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/Django-5.0.8-py3.11.egg-info running install_scripts Installing django-admin script to /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/bin + rm -rfv /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/bin/__pycache__ + pathfix.py -pni '/usr/bin/python3 -s' /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/manage.py-tpl /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11/site-packages/django/conf/project_template/manage.py-tpl: updating + mkdir -p /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/man/man1/ + cp -p docs/man/django-admin.1 /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/man/man1/ ++ pkg-config --variable=completionsdir bash-completion + bashcompdir=/usr/share/bash-completion/completions + mkdir -p /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions + install -m 0644 -p extras/django_bash_completion /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions/django-admin.py + for file in django-admin django-admin-3 django-admin-3.11 python3-django-admin manage.py + ln -s django-admin.py /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions/django-admin + for file in django-admin django-admin-3 django-admin-3.11 python3-django-admin manage.py + ln -s django-admin.py /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions/django-admin-3 + for file in django-admin django-admin-3 django-admin-3.11 python3-django-admin manage.py + ln -s django-admin.py /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions/django-admin-3.11 + for file in django-admin django-admin-3 django-admin-3.11 python3-django-admin manage.py + ln -s django-admin.py /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions/python3-django-admin + for file in django-admin django-admin-3 django-admin-3.11 python3-django-admin manage.py + ln -s django-admin.py /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/bash-completion/completions/manage.py + ln -s ./django-admin /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/bin/django-admin-3 + ln -s ./django-admin /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/bin/django-admin-3.11 + ln -s ./django-admin /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/bin/python3-django-admin + find /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch -name '*.po' -delete + /usr/bin/find-debuginfo -j32 --strict-build-id -m -i --build-id-seed 5.0.8-1.oc9 --unique-debug-suffix -5.0.8-1.oc9.noarch --unique-debug-src-base python-django-5.0.8-1.oc9.noarch -S debugsourcefiles.list /builddir/build/BUILD/django-5.0.8 find: 'debug': No such file or directory + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/OpenCloudOS/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/OpenCloudOS/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/OpenCloudOS/brp-mangle-shebangs + /usr/lib/rpm/OpenCloudOS/brp-python-bytecompile '' 1 0 Bytecompiling .py files below /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/lib/python3.11 using python3.11 + /usr/lib/rpm/OpenCloudOS/brp-python-hardlink Processing files: python-django-bash-completion-5.0.8-1.oc9.noarch Provides: python-django-bash-completion = 5.0.8-1.oc9 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Processing files: python3-django-5.0.8-1.oc9.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.EwqfPm + umask 022 + cd /builddir/build/BUILD + cd django-5.0.8 + DOCDIR=/builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/doc/python3-django + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/doc/python3-django + cp -pr AUTHORS /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/doc/python3-django + cp -pr README.rst /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/doc/python3-django + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.WxNuNi + umask 022 + cd /builddir/build/BUILD + cd django-5.0.8 + LICENSEDIR=/builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/licenses/python3-django + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/licenses/python3-django + cp -pr LICENSE /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch/usr/share/licenses/python3-django + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-Django python-django = 5.0.8-1.oc9 python3-django python3-django = 5.0.8-1.oc9 python3.11-django = 5.0.8-1.oc9 python3.11dist(django) = 5.0.8 python3dist(django) = 5.0.8 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: (python3.11dist(asgiref) < 4~~ with python3.11dist(asgiref) >= 3.7) /usr/bin/python3 python(abi) = 3.11 python3.11dist(sqlparse) >= 0.3.1 Obsoletes: python3.11-django < 5.0.8-1.oc9 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-5.0.8-1.oc9.noarch Wrote: /builddir/build/RPMS/python-django-bash-completion-5.0.8-1.oc9.noarch.rpm Wrote: /builddir/build/RPMS/python3-django-5.0.8-1.oc9.noarch.rpm Child return code was: 0