Warning: Permanently added '54.167.62.118' (ED25519) to the list of known hosts.
Running (timeout=18000): unbuffer mock --spec /var/lib/copr-rpmbuild/workspace/workdir-lhllgb2w/python-django4.2/python-django4.2.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-lhllgb2w/python-django4.2 --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1748943842.640973 -r /var/lib/copr-rpmbuild/results/configs/child.cfg
INFO: mock.py version 6.2 starting (python version = 3.13.0, NVR = mock-6.2-1.fc41), args: /usr/libexec/mock/mock --spec /var/lib/copr-rpmbuild/workspace/workdir-lhllgb2w/python-django4.2/python-django4.2.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-lhllgb2w/python-django4.2 --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1748943842.640973 -r /var/lib/copr-rpmbuild/results/configs/child.cfg
Start(bootstrap): init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish(bootstrap): init plugins
Start: init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish: init plugins
INFO: Signal handler active
Start: run
INFO: Start(/var/lib/copr-rpmbuild/workspace/workdir-lhllgb2w/python-django4.2/python-django4.2.spec)  Config(fedora-rawhide-x86_64)
Start: clean chroot
Finish: clean chroot
Mock Version: 6.2
INFO: Mock Version: 6.2
Start(bootstrap): chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1748943842.640973/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Guessed host environment type: unknown
INFO: Using container image: registry.fedoraproject.org/fedora:rawhide
INFO: Pulling image: registry.fedoraproject.org/fedora:rawhide
INFO: Tagging container image as mock-bootstrap-8d517e4f-cbca-4881-a260-2bb0eb29d5fc
INFO: Checking that a0a6c271b15cccce9f614e595b19f3aa040b118c6c5a7ea25ac8526cbc89023c image matches host's architecture
INFO: Copy content of container a0a6c271b15cccce9f614e595b19f3aa040b118c6c5a7ea25ac8526cbc89023c to /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1748943842.640973/root
INFO: mounting a0a6c271b15cccce9f614e595b19f3aa040b118c6c5a7ea25ac8526cbc89023c with podman image mount
INFO: image a0a6c271b15cccce9f614e595b19f3aa040b118c6c5a7ea25ac8526cbc89023c as /var/lib/containers/storage/overlay/924ef891ec91ee0771a2b9d0657c1a1c351e60cb77aadd56573546c5375767d7/merged
INFO: umounting image a0a6c271b15cccce9f614e595b19f3aa040b118c6c5a7ea25ac8526cbc89023c (/var/lib/containers/storage/overlay/924ef891ec91ee0771a2b9d0657c1a1c351e60cb77aadd56573546c5375767d7/merged) with podman image umount
INFO: Removing image mock-bootstrap-8d517e4f-cbca-4881-a260-2bb0eb29d5fc
INFO: Package manager dnf5 detected and used (fallback)
INFO: Not updating bootstrap chroot, bootstrap_image_ready=True
Start(bootstrap): creating root cache
Finish(bootstrap): creating root cache
Finish(bootstrap): chroot init
Start: chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1748943842.640973/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Package manager dnf5 detected and used (direct choice)
INFO: Buildroot is handled by package management downloaded with a bootstrap image:
  rpm-5.99.90-5.fc43.x86_64
  rpm-sequoia-1.8.0-1.fc43.x86_64
  dnf5-5.2.13.1-2.fc43.x86_64
  dnf5-plugins-5.2.13.1-2.fc43.x86_64
Start: installing minimal buildroot with dnf5
Updating and loading repositories:
 fedora                                 100% |  25.1 MiB/s |  21.7 MiB |  00m01s
>>> Downloading successful, but checksum doesn't match. Calculated: ba9fffe2176d
 Copr repository                        100% |  28.0 MiB/s |   5.7 MiB |  00m00s
Repositories loaded.
Package                            Arch   Version                    Repository      Size
Installing group/module packages:
 bash                              x86_64 5.2.37-3.fc43              fedora       8.2 MiB
 bzip2                             x86_64 1.0.8-20.fc42              fedora      99.3 KiB
 coreutils                         x86_64 9.7-3.fc43                 fedora       5.4 MiB
 cpio                              x86_64 2.15-2.fc41                fedora       1.1 MiB
 diffutils                         x86_64 3.12-2.fc43                fedora       1.6 MiB
 fedora-release-common             noarch 43-0.16                    fedora      20.4 KiB
 findutils                         x86_64 1:4.10.0-5.fc42            fedora       1.9 MiB
 gawk                              x86_64 5.3.2-1.fc43               fedora       1.8 MiB
 glibc-minimal-langpack            x86_64 2.41.9000-15.fc43          fedora       0.0   B
 grep                              x86_64 3.12-1.fc43                fedora       1.0 MiB
 gzip                              x86_64 1.13-3.fc42                fedora     392.9 KiB
 info                              x86_64 7.2-3.fc42                 fedora     357.9 KiB
 patch                             x86_64 2.8-1.fc43                 fedora     226.8 KiB
 redhat-rpm-config                 noarch 343-6.fc43                 fedora     181.4 KiB
 rpm-build                         x86_64 5.99.90-5.fc43             fedora     281.7 KiB
 sed                               x86_64 4.9-4.fc42                 fedora     857.3 KiB
 shadow-utils                      x86_64 2:4.17.4-1.fc43            fedora       4.0 MiB
 tar                               x86_64 2:1.35-5.fc42              fedora       3.0 MiB
 unzip                             x86_64 6.0-66.fc42                fedora     390.3 KiB
 util-linux                        x86_64 2.40.4-7.fc43              fedora       3.4 MiB
 which                             x86_64 2.23-1.fc42                fedora      83.4 KiB
 xz                                x86_64 1:5.8.1-1.fc43             fedora       1.3 MiB
Installing dependencies:
 add-determinism                   x86_64 0.6.0-1.fc43               fedora       2.5 MiB
 alternatives                      x86_64 1.33-1.fc43                fedora      62.2 KiB
 ansible-srpm-macros               noarch 1-17.1.fc42                fedora      35.7 KiB
 audit-libs                        x86_64 4.0.4-2.fc43               fedora     351.2 KiB
 binutils                          x86_64 2.44-3.fc43                fedora      25.9 MiB
 build-reproducibility-srpm-macros noarch 0.6.0-1.fc43               fedora     735.0   B
 bzip2-libs                        x86_64 1.0.8-20.fc42              fedora      84.6 KiB
 ca-certificates                   noarch 2024.2.69_v8.0.401-5.fc42  fedora       2.6 MiB
 coreutils-common                  x86_64 9.7-3.fc43                 fedora      11.3 MiB
 crypto-policies                   noarch 20250402-2.git86c0178.fc43 fedora     141.5 KiB
 curl                              x86_64 8.14.0-1.fc43              fedora     469.9 KiB
 cyrus-sasl-lib                    x86_64 2.1.28-30.fc42             fedora       2.3 MiB
 debugedit                         x86_64 5.1-6.fc43                 fedora     192.7 KiB
 dwz                               x86_64 0.15-9.fc42                fedora     291.0 KiB
 ed                                x86_64 1.21-2.fc42                fedora     146.5 KiB
 efi-srpm-macros                   noarch 6-3.fc43                   fedora      40.1 KiB
 elfutils                          x86_64 0.193-2.fc43               fedora       2.9 MiB
 elfutils-debuginfod-client        x86_64 0.193-2.fc43               fedora      83.9 KiB
 elfutils-default-yama-scope       noarch 0.193-2.fc43               fedora       1.8 KiB
 elfutils-libelf                   x86_64 0.193-2.fc43               fedora       1.2 MiB
 elfutils-libs                     x86_64 0.193-2.fc43               fedora     683.4 KiB
 fedora-gpg-keys                   noarch 43-0.2                     fedora     129.0 KiB
 fedora-release                    noarch 43-0.16                    fedora       0.0   B
 fedora-release-identity-basic     noarch 43-0.16                    fedora     664.0   B
 fedora-repos                      noarch 43-0.2                     fedora       4.9 KiB
 fedora-repos-rawhide              noarch 43-0.2                     fedora       2.2 KiB
 file                              x86_64 5.46-3.fc43                copr_base  100.2 KiB
 file-libs                         x86_64 5.46-3.fc43                copr_base   11.9 MiB
 filesystem                        x86_64 3.18-44.fc43               fedora     112.0   B
 filesystem-srpm-macros            noarch 3.18-44.fc43               fedora      38.2 KiB
 fonts-srpm-macros                 noarch 1:2.0.5-22.fc43            fedora      55.8 KiB
 forge-srpm-macros                 noarch 0.4.0-2.fc42               fedora      38.9 KiB
 fpc-srpm-macros                   noarch 1.3-14.fc42                fedora     144.0   B
 gdb-minimal                       x86_64 16.3-1.fc43                fedora      13.2 MiB
 gdbm-libs                         x86_64 1:1.23-9.fc42              fedora     129.9 KiB
 ghc-srpm-macros                   noarch 1.9.2-2.fc42               fedora     779.0   B
 glibc                             x86_64 2.41.9000-15.fc43          fedora       6.7 MiB
 glibc-common                      x86_64 2.41.9000-15.fc43          fedora       1.0 MiB
 glibc-gconv-extra                 x86_64 2.41.9000-15.fc43          fedora       7.2 MiB
 gmp                               x86_64 1:6.3.0-3.fc43             fedora     819.2 KiB
 gnat-srpm-macros                  noarch 6-7.fc42                   fedora       1.0 KiB
 gnupg2                            x86_64 2.4.8-2.fc43               fedora       6.5 MiB
 gnupg2-dirmngr                    x86_64 2.4.8-2.fc43               fedora     618.4 KiB
 gnupg2-gpg-agent                  x86_64 2.4.8-2.fc43               fedora     671.4 KiB
 gnupg2-gpgconf                    x86_64 2.4.8-2.fc43               fedora     250.0 KiB
 gnupg2-keyboxd                    x86_64 2.4.8-2.fc43               fedora     201.4 KiB
 gnupg2-verify                     x86_64 2.4.8-2.fc43               fedora     348.5 KiB
 gnutls                            x86_64 3.8.9-5.fc43               fedora       3.6 MiB
 go-srpm-macros                    noarch 3.6.0-7.fc43               fedora      60.8 KiB
 gpgverify                         noarch 2.1-3.fc43                 fedora       8.7 KiB
 ima-evm-utils-libs                x86_64 1.6.2-5.fc43               fedora      60.7 KiB
 jansson                           x86_64 2.14-2.fc42                fedora      93.1 KiB
 java-srpm-macros                  noarch 1-3.fc43                   fedora     102.0   B
 json-c                            x86_64 0.18-2.fc42                fedora      86.7 KiB
 kernel-srpm-macros                noarch 1.0-25.fc42                fedora       1.9 KiB
 keyutils-libs                     x86_64 1.6.3-5.fc42               fedora      58.3 KiB
 krb5-libs                         x86_64 1.21.3-5.fc42              fedora       2.3 MiB
 libacl                            x86_64 2.3.2-3.fc42               fedora      38.3 KiB
 libarchive                        x86_64 3.7.7-4.fc43               fedora     930.6 KiB
 libassuan                         x86_64 2.5.7-3.fc42               fedora     167.8 KiB
 libattr                           x86_64 2.5.2-5.fc42               fedora      27.1 KiB
 libblkid                          x86_64 2.40.4-7.fc43              fedora     262.4 KiB
 libbrotli                         x86_64 1.1.0-7.fc43               copr_base  833.3 KiB
 libcap                            x86_64 2.76-1.fc43                fedora     209.2 KiB
 libcap-ng                         x86_64 0.8.5-4.fc42               fedora      72.9 KiB
 libcom_err                        x86_64 1.47.2-3.fc42              fedora      67.1 KiB
 libcurl                           x86_64 8.14.0-1.fc43              fedora     895.2 KiB
 libeconf                          x86_64 0.7.6-1.fc43               fedora      64.6 KiB
 libevent                          x86_64 2.1.12-15.fc42             fedora     903.1 KiB
 libfdisk                          x86_64 2.40.4-7.fc43              fedora     372.3 KiB
 libffi                            x86_64 3.4.8-1.fc43               fedora      83.0 KiB
 libfsverity                       x86_64 1.6-2.fc42                 fedora      32.5 KiB
 libgcc                            x86_64 15.1.1-2.fc43              fedora     266.6 KiB
 libgcrypt                         x86_64 1.11.1-1.fc43              fedora       1.6 MiB
 libgomp                           x86_64 15.1.1-2.fc43              fedora     539.1 KiB
 libgpg-error                      x86_64 1.55-1.fc43                fedora     915.3 KiB
 libidn2                           x86_64 2.3.8-1.fc43               fedora     552.5 KiB
 libksba                           x86_64 1.6.7-3.fc42               fedora     402.5 KiB
 libmount                          x86_64 2.40.4-7.fc43              fedora     356.2 KiB
 libnghttp2                        x86_64 1.65.0-1.fc43              fedora     162.2 KiB
 libpkgconf                        x86_64 2.3.0-2.fc42               fedora      78.1 KiB
 libpsl                            x86_64 0.21.5-5.fc42              fedora      76.4 KiB
 libselinux                        x86_64 3.8-3.fc43                 copr_base  193.1 KiB
 libsemanage                       x86_64 3.8.1-2.fc43               copr_base  304.4 KiB
 libsepol                          x86_64 3.8-1.fc42                 fedora     826.0 KiB
 libsmartcols                      x86_64 2.40.4-7.fc43              fedora     180.4 KiB
 libssh                            x86_64 0.11.1-4.fc42              fedora     565.5 KiB
 libssh-config                     noarch 0.11.1-4.fc42              fedora     277.0   B
 libstdc++                         x86_64 15.1.1-2.fc43              fedora       2.8 MiB
 libtasn1                          x86_64 4.20.0-1.fc43              fedora     176.3 KiB
 libtool-ltdl                      x86_64 2.5.4-4.fc42               fedora      70.1 KiB
 libunistring                      x86_64 1.1-9.fc42                 fedora       1.7 MiB
 libusb1                           x86_64 1.0.28-2.fc43              fedora     171.0 KiB
 libuuid                           x86_64 2.40.4-7.fc43              fedora      37.3 KiB
 libverto                          x86_64 0.3.2-10.fc42              fedora      25.4 KiB
 libxcrypt                         x86_64 4.4.38-7.fc43              fedora     284.5 KiB
 libxml2                           x86_64 2.12.10-1.fc43             fedora       1.7 MiB
 libzstd                           x86_64 1.5.7-1.fc43               fedora     807.8 KiB
 lua-libs                          x86_64 5.4.7-3.fc43               fedora     276.9 KiB
 lua-srpm-macros                   noarch 1-15.fc42                  fedora       1.3 KiB
 lz4-libs                          x86_64 1.10.0-2.fc42              fedora     157.4 KiB
 mpfr                              x86_64 4.2.2-1.fc43               fedora     828.8 KiB
 ncurses-base                      noarch 6.5-5.20250125.fc42        fedora     326.8 KiB
 ncurses-libs                      x86_64 6.5-5.20250125.fc42        fedora     946.3 KiB
 nettle                            x86_64 3.10.1-1.fc43              fedora     790.5 KiB
 npth                              x86_64 1.8-2.fc42                 fedora      49.6 KiB
 ocaml-srpm-macros                 noarch 10-4.fc42                  fedora       1.9 KiB
 openblas-srpm-macros              noarch 2-19.fc42                  fedora     112.0   B
 openldap                          x86_64 2.6.9-5.fc43               fedora     655.1 KiB
 openssl-libs                      x86_64 1:3.5.0-3.fc43             fedora       8.9 MiB
 p11-kit                           x86_64 0.25.5-8.fc43              fedora       2.2 MiB
 p11-kit-trust                     x86_64 0.25.5-8.fc43              fedora     395.5 KiB
 package-notes-srpm-macros         noarch 0.5-13.fc42                fedora       1.6 KiB
 pam-libs                          x86_64 1.7.0-4.fc42               fedora     126.7 KiB
 pcre2                             x86_64 10.45-1.fc43               fedora     697.7 KiB
 pcre2-syntax                      noarch 10.45-1.fc43               fedora     273.9 KiB
 perl-srpm-macros                  noarch 1-57.fc42                  fedora     861.0   B
 pkgconf                           x86_64 2.3.0-2.fc42               fedora      88.5 KiB
 pkgconf-m4                        noarch 2.3.0-2.fc42               fedora      14.4 KiB
 pkgconf-pkg-config                x86_64 2.3.0-2.fc42               fedora     989.0   B
 popt                              x86_64 1.19-8.fc42                fedora     132.8 KiB
 publicsuffix-list-dafsa           noarch 20250116-1.fc42            fedora      68.5 KiB
 pyproject-srpm-macros             noarch 1.18.1-1.fc43              copr_base    1.9 KiB
 python-srpm-macros                noarch 3.13-5.fc43                fedora      51.7 KiB
 qt5-srpm-macros                   noarch 5.15.17-1.fc43             fedora     500.0   B
 qt6-srpm-macros                   noarch 6.9.0-2.fc43               fedora     464.0   B
 readline                          x86_64 8.2-13.fc43                fedora     485.0 KiB
 rpm                               x86_64 5.99.90-5.fc43             fedora       3.1 MiB
 rpm-build-libs                    x86_64 5.99.90-5.fc43             fedora     264.4 KiB
 rpm-libs                          x86_64 5.99.90-5.fc43             fedora     929.8 KiB
 rpm-sequoia                       x86_64 1.8.0-1.fc43               fedora       2.5 MiB
 rpm-sign-libs                     x86_64 5.99.90-5.fc43             fedora      39.7 KiB
 rust-srpm-macros                  noarch 26.3-4.fc42                fedora       4.8 KiB
 setup                             noarch 2.15.0-25.fc43             fedora     725.0 KiB
 sqlite-libs                       x86_64 3.49.2-1.fc43              fedora       1.5 MiB
 systemd-libs                      x86_64 257.6-1.fc43               fedora       2.2 MiB
 systemd-standalone-sysusers       x86_64 257.6-1.fc43               fedora     277.3 KiB
 tpm2-tss                          x86_64 4.1.3-7.fc43               fedora       1.6 MiB
 tree-sitter-srpm-macros           noarch 0.2.4-1.fc43               fedora       7.5 KiB
 util-linux-core                   x86_64 2.40.4-7.fc43              fedora       1.4 MiB
 xxhash-libs                       x86_64 0.8.3-2.fc42               fedora      90.2 KiB
 xz-libs                           x86_64 1:5.8.1-1.fc43             fedora     217.8 KiB
 zig-srpm-macros                   noarch 1-4.fc42                   fedora       1.1 KiB
 zip                               x86_64 3.0-43.fc42                fedora     698.5 KiB
 zlib-ng-compat                    x86_64 2.2.4-2.fc43               fedora     137.6 KiB
 zstd                              x86_64 1.5.7-1.fc43               fedora       1.7 MiB
Installing groups:
 Buildsystem building group                                                              

Transaction Summary:
 Installing:       168 packages

Total size of inbound packages is 58 MiB. Need to download 58 MiB.
After this operation, 197 MiB extra will be used (install 197 MiB, remove 0 B).
[  1/168] bzip2-0:1.0.8-20.fc42.x86_64  100% |   5.6 MiB/s |  52.1 KiB |  00m00s
[  2/168] cpio-0:2.15-2.fc41.x86_64     100% |  57.0 MiB/s | 291.8 KiB |  00m00s
[  3/168] bash-0:5.2.37-3.fc43.x86_64   100% | 113.3 MiB/s |   1.8 MiB |  00m00s
[  4/168] coreutils-0:9.7-3.fc43.x86_64 100% |  67.1 MiB/s |   1.1 MiB |  00m00s
[  5/168] diffutils-0:3.12-2.fc43.x86_6 100% |  95.9 MiB/s | 392.7 KiB |  00m00s
[  6/168] fedora-release-common-0:43-0. 100% |  12.6 MiB/s |  25.9 KiB |  00m00s
[  7/168] glibc-minimal-langpack-0:2.41 100% |  26.0 MiB/s |  26.7 KiB |  00m00s
[  8/168] findutils-1:4.10.0-5.fc42.x86 100% | 269.3 MiB/s | 551.5 KiB |  00m00s
[  9/168] grep-0:3.12-1.fc43.x86_64     100% | 146.2 MiB/s | 299.5 KiB |  00m00s
[ 10/168] gzip-0:1.13-3.fc42.x86_64     100% |  83.2 MiB/s | 170.4 KiB |  00m00s
[ 11/168] info-0:7.2-3.fc42.x86_64      100% |  89.8 MiB/s | 183.8 KiB |  00m00s
[ 12/168] patch-0:2.8-1.fc43.x86_64     100% | 111.0 MiB/s | 113.7 KiB |  00m00s
[ 13/168] redhat-rpm-config-0:343-6.fc4 100% |  38.8 MiB/s |  79.4 KiB |  00m00s
[ 14/168] rpm-build-0:5.99.90-5.fc43.x8 100% |  65.1 MiB/s | 133.2 KiB |  00m00s
[ 15/168] sed-0:4.9-4.fc42.x86_64       100% | 154.9 MiB/s | 317.3 KiB |  00m00s
[ 16/168] shadow-utils-2:4.17.4-1.fc43. 100% | 264.6 MiB/s |   1.3 MiB |  00m00s
[ 17/168] tar-2:1.35-5.fc42.x86_64      100% | 140.4 MiB/s | 862.5 KiB |  00m00s
[ 18/168] unzip-0:6.0-66.fc42.x86_64    100% |  30.0 MiB/s | 184.6 KiB |  00m00s
[ 19/168] which-0:2.23-1.fc42.x86_64    100% |  13.6 MiB/s |  41.7 KiB |  00m00s
[ 20/168] xz-1:5.8.1-1.fc43.x86_64      100% | 279.5 MiB/s | 572.5 KiB |  00m00s
[ 21/168] gawk-0:5.3.2-1.fc43.x86_64    100% | 281.2 MiB/s |   1.1 MiB |  00m00s
[ 22/168] util-linux-0:2.40.4-7.fc43.x8 100% | 192.3 MiB/s |   1.2 MiB |  00m00s
[ 23/168] filesystem-0:3.18-44.fc43.x86 100% | 222.1 MiB/s |   1.3 MiB |  00m00s
[ 24/168] glibc-0:2.41.9000-15.fc43.x86 100% | 273.1 MiB/s |   2.2 MiB |  00m00s
[ 25/168] bzip2-libs-0:1.0.8-20.fc42.x8 100% |  10.6 MiB/s |  43.6 KiB |  00m00s
[ 26/168] ncurses-libs-0:6.5-5.20250125 100% |  46.7 MiB/s | 335.0 KiB |  00m00s
[ 27/168] coreutils-common-0:9.7-3.fc43 100% | 350.0 MiB/s |   2.1 MiB |  00m00s
[ 28/168] gmp-1:6.3.0-3.fc43.x86_64     100% |  52.4 MiB/s | 322.2 KiB |  00m00s
[ 29/168] libacl-0:2.3.2-3.fc42.x86_64  100% |   3.7 MiB/s |  23.0 KiB |  00m00s
[ 30/168] libattr-0:2.5.2-5.fc42.x86_64 100% |  16.7 MiB/s |  17.1 KiB |  00m00s
[ 31/168] libcap-0:2.76-1.fc43.x86_64   100% |  28.3 MiB/s |  86.9 KiB |  00m00s
[ 32/168] systemd-libs-0:257.6-1.fc43.x 100% | 128.5 MiB/s | 789.6 KiB |  00m00s
[ 33/168] openssl-libs-1:3.5.0-3.fc43.x 100% | 289.7 MiB/s |   2.6 MiB |  00m00s
[ 34/168] fedora-repos-0:43-0.2.noarch  100% |   1.5 MiB/s |   9.2 KiB |  00m00s
[ 35/168] glibc-common-0:2.41.9000-15.f 100% |  61.2 MiB/s | 313.3 KiB |  00m00s
[ 36/168] pcre2-0:10.45-1.fc43.x86_64   100% | 128.3 MiB/s | 262.8 KiB |  00m00s
[ 37/168] ed-0:1.21-2.fc42.x86_64       100% |  26.7 MiB/s |  82.0 KiB |  00m00s
[ 38/168] ansible-srpm-macros-0:1-17.1. 100% |  19.8 MiB/s |  20.3 KiB |  00m00s
[ 39/168] build-reproducibility-srpm-ma 100% |  11.4 MiB/s |  11.7 KiB |  00m00s
[ 40/168] efi-srpm-macros-0:6-3.fc43.no 100% |  22.0 MiB/s |  22.5 KiB |  00m00s
[ 41/168] dwz-0:0.15-9.fc42.x86_64      100% |  66.3 MiB/s | 135.7 KiB |  00m00s
[ 42/168] filesystem-srpm-macros-0:3.18 100% |  25.4 MiB/s |  26.0 KiB |  00m00s
[ 43/168] fonts-srpm-macros-1:2.0.5-22. 100% |  26.5 MiB/s |  27.2 KiB |  00m00s
[ 44/168] forge-srpm-macros-0:0.4.0-2.f 100% |   0.0   B/s |  19.9 KiB |  00m00s
[ 45/168] fpc-srpm-macros-0:1.3-14.fc42 100% |   0.0   B/s |   8.0 KiB |  00m00s
[ 46/168] ghc-srpm-macros-0:1.9.2-2.fc4 100% |   8.9 MiB/s |   9.2 KiB |  00m00s
[ 47/168] gnat-srpm-macros-0:6-7.fc42.n 100% |   8.4 MiB/s |   8.6 KiB |  00m00s
[ 48/168] go-srpm-macros-0:3.6.0-7.fc43 100% |  27.0 MiB/s |  27.6 KiB |  00m00s
[ 49/168] java-srpm-macros-0:1-3.fc43.n 100% |   7.0 MiB/s |   7.1 KiB |  00m00s
[ 50/168] kernel-srpm-macros-0:1.0-25.f 100% |   9.6 MiB/s |   9.9 KiB |  00m00s
[ 51/168] lua-srpm-macros-0:1-15.fc42.n 100% |   8.7 MiB/s |   8.9 KiB |  00m00s
[ 52/168] ocaml-srpm-macros-0:10-4.fc42 100% |   9.0 MiB/s |   9.2 KiB |  00m00s
[ 53/168] openblas-srpm-macros-0:2-19.f 100% |   0.0   B/s |   7.8 KiB |  00m00s
[ 54/168] package-notes-srpm-macros-0:0 100% |   9.0 MiB/s |   9.3 KiB |  00m00s
[ 55/168] perl-srpm-macros-0:1-57.fc42. 100% |   8.3 MiB/s |   8.5 KiB |  00m00s
[ 56/168] python-srpm-macros-0:3.13-5.f 100% |  22.7 MiB/s |  23.2 KiB |  00m00s
[ 57/168] qt5-srpm-macros-0:5.15.17-1.f 100% |   8.5 MiB/s |   8.7 KiB |  00m00s
[ 58/168] qt6-srpm-macros-0:6.9.0-2.fc4 100% |   9.2 MiB/s |   9.4 KiB |  00m00s
[ 59/168] rust-srpm-macros-0:26.3-4.fc4 100% |  11.4 MiB/s |  11.7 KiB |  00m00s
[ 60/168] rpm-0:5.99.90-5.fc43.x86_64   100% | 180.9 MiB/s | 555.8 KiB |  00m00s
[ 61/168] tree-sitter-srpm-macros-0:0.2 100% |  12.2 MiB/s |  12.5 KiB |  00m00s
[ 62/168] zig-srpm-macros-0:1-4.fc42.no 100% |   8.1 MiB/s |   8.2 KiB |  00m00s
[ 63/168] zip-0:3.0-43.fc42.x86_64      100% | 128.7 MiB/s | 263.5 KiB |  00m00s
[ 64/168] debugedit-0:5.1-6.fc43.x86_64 100% |  38.4 MiB/s |  78.7 KiB |  00m00s
[ 65/168] elfutils-0:0.193-2.fc43.x86_6 100% | 186.0 MiB/s | 571.5 KiB |  00m00s
[ 66/168] elfutils-libelf-0:0.193-2.fc4 100% | 101.5 MiB/s | 207.9 KiB |  00m00s
[ 67/168] libarchive-0:3.7.7-4.fc43.x86 100% | 201.0 MiB/s | 411.7 KiB |  00m00s
[ 68/168] libgcc-0:15.1.1-2.fc43.x86_64 100% |  62.3 MiB/s | 127.5 KiB |  00m00s
[ 69/168] libstdc++-0:15.1.1-2.fc43.x86 100% | 297.1 MiB/s | 912.8 KiB |  00m00s
[ 70/168] popt-0:1.19-8.fc42.x86_64     100% |  21.5 MiB/s |  66.0 KiB |  00m00s
[ 71/168] readline-0:8.2-13.fc43.x86_64 100% | 104.0 MiB/s | 212.9 KiB |  00m00s
[ 72/168] rpm-build-libs-0:5.99.90-5.fc 100% |  62.2 MiB/s | 127.4 KiB |  00m00s
[ 73/168] rpm-libs-0:5.99.90-5.fc43.x86 100% | 130.2 MiB/s | 399.9 KiB |  00m00s
[ 74/168] zstd-0:1.5.7-1.fc43.x86_64    100% | 158.1 MiB/s | 485.8 KiB |  00m00s
[ 75/168] libeconf-0:0.7.6-1.fc43.x86_6 100% |  34.3 MiB/s |  35.2 KiB |  00m00s
[ 76/168] audit-libs-0:4.0.4-2.fc43.x86 100% |  63.2 MiB/s | 129.4 KiB |  00m00s
[ 77/168] pam-libs-0:1.7.0-4.fc42.x86_6 100% |  57.0 MiB/s |  58.3 KiB |  00m00s
[ 78/168] libxcrypt-0:4.4.38-7.fc43.x86 100% |  62.1 MiB/s | 127.2 KiB |  00m00s
[ 79/168] setup-0:2.15.0-25.fc43.noarch 100% |  76.9 MiB/s | 157.6 KiB |  00m00s
[ 80/168] xz-libs-1:5.8.1-1.fc43.x86_64 100% | 110.4 MiB/s | 113.0 KiB |  00m00s
[ 81/168] mpfr-0:4.2.2-1.fc43.x86_64    100% | 169.3 MiB/s | 346.7 KiB |  00m00s
[ 82/168] libcap-ng-0:0.8.5-4.fc42.x86_ 100% |  15.7 MiB/s |  32.2 KiB |  00m00s
[ 83/168] libblkid-0:2.40.4-7.fc43.x86_ 100% |  39.9 MiB/s | 122.5 KiB |  00m00s
[ 84/168] libfdisk-0:2.40.4-7.fc43.x86_ 100% |  77.2 MiB/s | 158.2 KiB |  00m00s
[ 85/168] libmount-0:2.40.4-7.fc43.x86_ 100% |  75.7 MiB/s | 155.0 KiB |  00m00s
[ 86/168] libsmartcols-0:2.40.4-7.fc43. 100% |  79.3 MiB/s |  81.2 KiB |  00m00s
[ 87/168] libuuid-0:2.40.4-7.fc43.x86_6 100% |  24.7 MiB/s |  25.3 KiB |  00m00s
[ 88/168] util-linux-core-0:2.40.4-7.fc 100% | 258.6 MiB/s | 529.5 KiB |  00m00s
[ 89/168] zlib-ng-compat-0:2.2.4-2.fc43 100% |  38.6 MiB/s |  79.1 KiB |  00m00s
[ 90/168] glibc-gconv-extra-0:2.41.9000 100% | 314.6 MiB/s |   1.6 MiB |  00m00s
[ 91/168] ncurses-base-0:6.5-5.20250125 100% |  21.5 MiB/s |  88.1 KiB |  00m00s
[ 92/168] ca-certificates-0:2024.2.69_v 100% | 184.6 MiB/s | 945.0 KiB |  00m00s
[ 93/168] crypto-policies-0:20250402-2. 100% |  31.7 MiB/s |  97.3 KiB |  00m00s
[ 94/168] fedora-gpg-keys-0:43-0.2.noar 100% |  66.7 MiB/s | 136.6 KiB |  00m00s
[ 95/168] fedora-repos-rawhide-0:43-0.2 100% |   8.6 MiB/s |   8.8 KiB |  00m00s
[ 96/168] pcre2-syntax-0:10.45-1.fc43.n 100% |  79.0 MiB/s | 161.7 KiB |  00m00s
[ 97/168] add-determinism-0:0.6.0-1.fc4 100% | 298.9 MiB/s | 918.3 KiB |  00m00s
[ 98/168] curl-0:8.14.0-1.fc43.x86_64   100% |  57.1 MiB/s | 234.0 KiB |  00m00s
[ 99/168] elfutils-libs-0:0.193-2.fc43. 100% |  88.0 MiB/s | 270.2 KiB |  00m00s
[100/168] elfutils-debuginfod-client-0: 100% |  23.0 MiB/s |  47.0 KiB |  00m00s
[101/168] libzstd-0:1.5.7-1.fc43.x86_64 100% |  76.9 MiB/s | 314.8 KiB |  00m00s
[102/168] lz4-libs-0:1.10.0-2.fc42.x86_ 100% |  25.4 MiB/s |  78.1 KiB |  00m00s
[103/168] libxml2-0:2.12.10-1.fc43.x86_ 100% | 166.7 MiB/s | 682.9 KiB |  00m00s
[104/168] libgomp-0:15.1.1-2.fc43.x86_6 100% | 178.3 MiB/s | 365.2 KiB |  00m00s
[105/168] lua-libs-0:5.4.7-3.fc43.x86_6 100% |  63.7 MiB/s | 130.4 KiB |  00m00s
[106/168] rpm-sign-libs-0:5.99.90-5.fc4 100% |  28.6 MiB/s |  29.2 KiB |  00m00s
[107/168] elfutils-default-yama-scope-0 100% |  12.3 MiB/s |  12.6 KiB |  00m00s
[108/168] rpm-sequoia-0:1.8.0-1.fc43.x8 100% | 305.6 MiB/s | 938.8 KiB |  00m00s
[109/168] sqlite-libs-0:3.49.2-1.fc43.x 100% | 185.4 MiB/s | 759.5 KiB |  00m00s
[110/168] json-c-0:0.18-2.fc42.x86_64   100% |  14.6 MiB/s |  44.9 KiB |  00m00s
[111/168] gnupg2-0:2.4.8-2.fc43.x86_64  100% | 328.9 MiB/s |   1.6 MiB |  00m00s
[112/168] ima-evm-utils-libs-0:1.6.2-5. 100% |   9.6 MiB/s |  29.5 KiB |  00m00s
[113/168] libfsverity-0:1.6-2.fc42.x86_ 100% |   6.1 MiB/s |  18.8 KiB |  00m00s
[114/168] gpgverify-0:2.1-3.fc43.noarch 100% |  10.5 MiB/s |  10.8 KiB |  00m00s
[115/168] gnupg2-dirmngr-0:2.4.8-2.fc43 100% | 134.2 MiB/s | 274.8 KiB |  00m00s
[116/168] gnupg2-gpg-agent-0:2.4.8-2.fc 100% | 133.3 MiB/s | 273.0 KiB |  00m00s
[117/168] gnupg2-gpgconf-0:2.4.8-2.fc43 100% |  56.2 MiB/s | 115.2 KiB |  00m00s
[118/168] gnupg2-keyboxd-0:2.4.8-2.fc43 100% |  92.5 MiB/s |  94.8 KiB |  00m00s
[119/168] gnupg2-verify-0:2.4.8-2.fc43. 100% | 167.3 MiB/s | 171.3 KiB |  00m00s
[120/168] libassuan-0:2.5.7-3.fc42.x86_ 100% |  66.0 MiB/s |  67.6 KiB |  00m00s
[121/168] libgcrypt-0:1.11.1-1.fc43.x86 100% | 291.1 MiB/s | 596.1 KiB |  00m00s
[122/168] npth-0:1.8-2.fc42.x86_64      100% |  25.2 MiB/s |  25.8 KiB |  00m00s
[123/168] libgpg-error-0:1.55-1.fc43.x8 100% | 119.2 MiB/s | 244.1 KiB |  00m00s
[124/168] tpm2-tss-0:4.1.3-7.fc43.x86_6 100% | 206.7 MiB/s | 423.4 KiB |  00m00s
[125/168] gnutls-0:3.8.9-5.fc43.x86_64  100% | 308.3 MiB/s |   1.2 MiB |  00m00s
[126/168] libksba-0:1.6.7-3.fc42.x86_64 100% |  39.6 MiB/s | 162.0 KiB |  00m00s
[127/168] openldap-0:2.6.9-5.fc43.x86_6 100% |  84.2 MiB/s | 258.6 KiB |  00m00s
[128/168] libusb1-0:1.0.28-2.fc43.x86_6 100% |  38.7 MiB/s |  79.3 KiB |  00m00s
[129/168] libidn2-0:2.3.8-1.fc43.x86_64 100% |  85.4 MiB/s | 174.8 KiB |  00m00s
[130/168] libtasn1-0:4.20.0-1.fc43.x86_ 100% |  73.2 MiB/s |  75.0 KiB |  00m00s
[131/168] libunistring-0:1.1-9.fc42.x86 100% | 176.6 MiB/s | 542.5 KiB |  00m00s
[132/168] nettle-0:3.10.1-1.fc43.x86_64 100% | 138.2 MiB/s | 424.6 KiB |  00m00s
[133/168] p11-kit-0:0.25.5-8.fc43.x86_6 100% | 119.2 MiB/s | 488.2 KiB |  00m00s
[134/168] cyrus-sasl-lib-0:2.1.28-30.fc 100% | 258.3 MiB/s | 793.5 KiB |  00m00s
[135/168] libevent-0:2.1.12-15.fc42.x86 100% |  84.7 MiB/s | 260.2 KiB |  00m00s
[136/168] libtool-ltdl-0:2.5.4-4.fc42.x 100% |  17.7 MiB/s |  36.2 KiB |  00m00s
[137/168] libffi-0:3.4.8-1.fc43.x86_64  100% |   0.0   B/s |  40.5 KiB |  00m00s
[138/168] gdbm-libs-1:1.23-9.fc42.x86_6 100% |  55.7 MiB/s |  57.0 KiB |  00m00s
[139/168] libsepol-0:3.8-1.fc42.x86_64  100% | 170.4 MiB/s | 348.9 KiB |  00m00s
[140/168] libselinux-0:3.8-3.fc43.x86_6 100% |  13.6 MiB/s |  97.2 KiB |  00m00s
[141/168] alternatives-0:1.33-1.fc43.x8 100% |   6.6 MiB/s |  40.5 KiB |  00m00s
[142/168] jansson-0:2.14-2.fc42.x86_64  100% |  11.2 MiB/s |  45.7 KiB |  00m00s
[143/168] binutils-0:2.44-3.fc43.x86_64 100% | 363.3 MiB/s |   5.8 MiB |  00m00s
[144/168] libsemanage-0:3.8.1-2.fc43.x8 100% |  17.3 MiB/s | 123.8 KiB |  00m00s
[145/168] pkgconf-pkg-config-0:2.3.0-2. 100% |   0.0   B/s |   9.9 KiB |  00m00s
[146/168] pkgconf-0:2.3.0-2.fc42.x86_64 100% |  43.8 MiB/s |  44.9 KiB |  00m00s
[147/168] file-libs-0:5.46-3.fc43.x86_6 100% | 103.8 MiB/s | 850.0 KiB |  00m00s
[148/168] pkgconf-m4-0:2.3.0-2.fc42.noa 100% |  13.9 MiB/s |  14.2 KiB |  00m00s
[149/168] file-0:5.46-3.fc43.x86_64     100% |  16.0 MiB/s |  49.2 KiB |  00m00s
[150/168] libpkgconf-0:2.3.0-2.fc42.x86 100% |  37.5 MiB/s |  38.4 KiB |  00m00s
[151/168] pyproject-srpm-macros-0:1.18. 100% |   7.1 MiB/s |  14.5 KiB |  00m00s
[152/168] fedora-release-0:43-0.16.noar 100% |  14.5 MiB/s |  14.9 KiB |  00m00s
[153/168] p11-kit-trust-0:0.25.5-8.fc43 100% |  64.7 MiB/s | 132.4 KiB |  00m00s
[154/168] xxhash-libs-0:0.8.3-2.fc42.x8 100% |  38.2 MiB/s |  39.1 KiB |  00m00s
[155/168] systemd-standalone-sysusers-0 100% |  65.6 MiB/s | 134.4 KiB |  00m00s
[156/168] fedora-release-identity-basic 100% |   3.1 MiB/s |  15.6 KiB |  00m00s
[157/168] gdb-minimal-0:16.3-1.fc43.x86 100% | 367.5 MiB/s |   4.4 MiB |  00m00s
[158/168] libcurl-0:8.14.0-1.fc43.x86_6 100% |  35.5 MiB/s | 399.7 KiB |  00m00s
[159/168] krb5-libs-0:1.21.3-5.fc42.x86 100% | 106.7 MiB/s | 764.7 KiB |  00m00s
[160/168] libnghttp2-0:1.65.0-1.fc43.x8 100% |  35.4 MiB/s |  72.6 KiB |  00m00s
[161/168] libpsl-0:0.21.5-5.fc42.x86_64 100% |  31.3 MiB/s |  64.0 KiB |  00m00s
[162/168] keyutils-libs-0:1.6.3-5.fc42. 100% |  30.8 MiB/s |  31.5 KiB |  00m00s
[163/168] libssh-0:0.11.1-4.fc42.x86_64 100% | 113.9 MiB/s | 233.3 KiB |  00m00s
[164/168] libcom_err-0:1.47.2-3.fc42.x8 100% |  26.3 MiB/s |  26.9 KiB |  00m00s
[165/168] libverto-0:0.3.2-10.fc42.x86_ 100% |  10.2 MiB/s |  20.8 KiB |  00m00s
[166/168] libssh-config-0:0.11.1-4.fc42 100% |   8.8 MiB/s |   9.0 KiB |  00m00s
[167/168] publicsuffix-list-dafsa-0:202 100% |  19.2 MiB/s |  58.8 KiB |  00m00s
[168/168] libbrotli-0:1.1.0-7.fc43.x86_ 100% | 110.5 MiB/s | 339.6 KiB |  00m00s
--------------------------------------------------------------------------------
[168/168] Total                         100% | 223.8 MiB/s |  58.4 MiB |  00m00s
Running transaction
Importing OpenPGP key 0x31645531:
 UserID     : "Fedora (43) <fedora-43-primary@fedoraproject.org>"
 Fingerprint: C6E7F081CF80E13146676E88829B606631645531
 From       : file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-43-primary
The key was successfully imported.
Importing OpenPGP key 0x31645531:
 UserID     : "Fedora (43) <fedora-43-primary@fedoraproject.org>"
 Fingerprint: C6E7F081CF80E13146676E88829B606631645531
 From       : file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-43-primary
The key was successfully imported.
Importing OpenPGP key 0x105EF944:
 UserID     : "Fedora (42) <fedora-42-primary@fedoraproject.org>"
 Fingerprint: B0F4950458F69E1150C6C5EDC8AC4916105EF944
 From       : file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-42-primary
The key was successfully imported.
Importing OpenPGP key 0x6D9F90A6:
 UserID     : "Fedora (44) <fedora-44-primary@fedoraproject.org>"
 Fingerprint: 36F612DCF27F7D1A48A835E4DBFCF71C6D9F90A6
 From       : file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-44-primary
The key was successfully imported.
[  1/170] Verify package files          100% |   1.7 KiB/s | 168.0   B |  00m00s
>>> Running pre-transaction scriptlet: filesystem-0:3.18-44.fc43.x86_64         
>>> Finished pre-transaction scriptlet: filesystem-0:3.18-44.fc43.x86_64        
>>> [RPM] /var/lib/mock/fedora-rawhide-x86_64-1748943842.640973/root/var/cache/d
[  2/170] Prepare transaction           100% |   4.3 KiB/s | 168.0   B |  00m00s
[  3/170] Installing libgcc-0:15.1.1-2. 100% | 262.0 MiB/s | 268.3 KiB |  00m00s
[  4/170] Installing libssh-config-0:0. 100% |   0.0   B/s | 816.0   B |  00m00s
[  5/170] Installing publicsuffix-list- 100% |   0.0   B/s |  69.2 KiB |  00m00s
[  6/170] Installing fedora-release-ide 100% |   0.0   B/s | 920.0   B |  00m00s
[  7/170] Installing fedora-gpg-keys-0: 100% |  42.9 MiB/s | 175.9 KiB |  00m00s
[  8/170] Installing fedora-repos-rawhi 100% |   0.0   B/s |   2.4 KiB |  00m00s
[  9/170] Installing fedora-repos-0:43- 100% |   0.0   B/s |   5.7 KiB |  00m00s
[ 10/170] Installing fedora-release-com 100% |  24.1 MiB/s |  24.7 KiB |  00m00s
[ 11/170] Installing fedora-release-0:4 100% |  17.3 KiB/s | 124.0   B |  00m00s
>>> Running sysusers scriptlet: setup-0:2.15.0-25.fc43.noarch                   
>>> Finished sysusers scriptlet: setup-0:2.15.0-25.fc43.noarch                  
>>> Scriptlet output:                                                           
>>> Creating group 'adm' with GID 4.                                            
>>> Creating group 'audio' with GID 63.                                         
>>> Creating group 'cdrom' with GID 11.                                         
>>> Creating group 'clock' with GID 103.                                        
>>> Creating group 'dialout' with GID 18.                                       
>>> Creating group 'disk' with GID 6.                                           
>>> Creating group 'floppy' with GID 19.                                        
>>> Creating group 'ftp' with GID 50.                                           
>>> Creating group 'games' with GID 20.                                         
>>> Creating group 'input' with GID 104.                                        
>>> Creating group 'kmem' with GID 9.                                           
>>> Creating group 'kvm' with GID 36.                                           
>>> Creating group 'lock' with GID 54.                                          
>>> Creating group 'lp' with GID 7.                                             
>>> Creating group 'mail' with GID 12.                                          
>>> Creating group 'man' with GID 15.                                           
>>> Creating group 'mem' with GID 8.                                            
>>> Creating group 'nobody' with GID 65534.                                     
>>> Creating group 'render' with GID 105.                                       
>>> Creating group 'root' with GID 0.                                           
>>> Creating group 'sgx' with GID 106.                                          
>>> Creating group 'sys' with GID 3.                                            
>>> Creating group 'tape' with GID 33.                                          
>>> Creating group 'tty' with GID 5.                                            
>>> Creating group 'users' with GID 100.                                        
>>> Creating group 'utmp' with GID 22.                                          
>>> Creating group 'video' with GID 39.                                         
>>> Creating group 'wheel' with GID 10.                                         
>>> Creating user 'adm' (adm) with UID 3 and GID 4.                             
>>> Creating group 'bin' with GID 1.                                            
>>> Creating user 'bin' (bin) with UID 1 and GID 1.                             
>>> Creating group 'daemon' with GID 2.                                         
>>> Creating user 'daemon' (daemon) with UID 2 and GID 2.                       
>>> Creating user 'ftp' (FTP User) with UID 14 and GID 50.                      
>>> Creating user 'games' (games) with UID 12 and GID 100.                      
>>> Creating user 'halt' (halt) with UID 7 and GID 0.                           
>>> Creating user 'lp' (lp) with UID 4 and GID 7.                               
>>> Creating user 'mail' (mail) with UID 8 and GID 12.                          
>>> Creating user 'nobody' (Kernel Overflow User) with UID 65534 and GID 65534. 
>>> Creating user 'operator' (operator) with UID 11 and GID 0.                  
>>> Creating user 'root' (Super User) with UID 0 and GID 0.                     
>>> Creating user 'shutdown' (shutdown) with UID 6 and GID 0.                   
>>> Creating user 'sync' (sync) with UID 5 and GID 0.                           
>>>                                                                             
[ 12/170] Installing setup-0:2.15.0-25. 100% |  54.9 MiB/s | 730.6 KiB |  00m00s
>>> [RPM] /etc/hosts created as /etc/hosts.rpmnew                               
[ 13/170] Installing filesystem-0:3.18- 100% |   2.8 MiB/s | 212.5 KiB |  00m00s
[ 14/170] Installing pkgconf-m4-0:2.3.0 100% |   0.0   B/s |  14.8 KiB |  00m00s
[ 15/170] Installing pcre2-syntax-0:10. 100% | 269.9 MiB/s | 276.4 KiB |  00m00s
[ 16/170] Installing ncurses-base-0:6.5 100% |  86.0 MiB/s | 352.2 KiB |  00m00s
[ 17/170] Installing bash-0:5.2.37-3.fc 100% | 272.7 MiB/s |   8.2 MiB |  00m00s
[ 18/170] Installing glibc-common-0:2.4 100% |  68.0 MiB/s |   1.0 MiB |  00m00s
[ 19/170] Installing glibc-gconv-extra- 100% | 292.5 MiB/s |   7.3 MiB |  00m00s
[ 20/170] Installing glibc-0:2.41.9000- 100% | 196.4 MiB/s |   6.7 MiB |  00m00s
[ 21/170] Installing ncurses-libs-0:6.5 100% | 310.1 MiB/s | 952.8 KiB |  00m00s
[ 22/170] Installing glibc-minimal-lang 100% |   0.0   B/s | 124.0   B |  00m00s
[ 23/170] Installing zlib-ng-compat-0:2 100% | 135.2 MiB/s | 138.4 KiB |  00m00s
[ 24/170] Installing bzip2-libs-0:1.0.8 100% |  83.7 MiB/s |  85.7 KiB |  00m00s
[ 25/170] Installing libgpg-error-0:1.5 100% |  64.3 MiB/s | 921.1 KiB |  00m00s
[ 26/170] Installing libstdc++-0:15.1.1 100% | 405.2 MiB/s |   2.8 MiB |  00m00s
[ 27/170] Installing xz-libs-1:5.8.1-1. 100% | 213.8 MiB/s | 218.9 KiB |  00m00s
[ 28/170] Installing libassuan-0:2.5.7- 100% | 165.6 MiB/s | 169.6 KiB |  00m00s
[ 29/170] Installing libgcrypt-0:1.11.1 100% | 393.8 MiB/s |   1.6 MiB |  00m00s
[ 30/170] Installing readline-0:8.2-13. 100% | 475.7 MiB/s | 487.1 KiB |  00m00s
[ 31/170] Installing gmp-1:6.3.0-3.fc43 100% | 401.1 MiB/s | 821.5 KiB |  00m00s
[ 32/170] Installing libuuid-0:2.40.4-7 100% |   0.0   B/s |  38.4 KiB |  00m00s
[ 33/170] Installing popt-0:1.19-8.fc42 100% |  68.1 MiB/s | 139.4 KiB |  00m00s
[ 34/170] Installing npth-0:1.8-2.fc42. 100% |   0.0   B/s |  50.7 KiB |  00m00s
[ 35/170] Installing libblkid-0:2.40.4- 100% | 257.2 MiB/s | 263.4 KiB |  00m00s
[ 36/170] Installing libxcrypt-0:4.4.38 100% | 280.4 MiB/s | 287.2 KiB |  00m00s
[ 37/170] Installing libzstd-0:1.5.7-1. 100% | 395.1 MiB/s | 809.1 KiB |  00m00s
[ 38/170] Installing elfutils-libelf-0: 100% | 388.8 MiB/s |   1.2 MiB |  00m00s
[ 39/170] Installing gnupg2-gpgconf-0:2 100% |  20.5 MiB/s | 252.1 KiB |  00m00s
[ 40/170] Installing libattr-0:2.5.2-5. 100% |   0.0   B/s |  28.1 KiB |  00m00s
[ 41/170] Installing libacl-0:2.3.2-3.f 100% |   0.0   B/s |  39.2 KiB |  00m00s
[ 42/170] Installing sqlite-libs-0:3.49 100% | 378.1 MiB/s |   1.5 MiB |  00m00s
[ 43/170] Installing libtasn1-0:4.20.0- 100% | 173.9 MiB/s | 178.1 KiB |  00m00s
[ 44/170] Installing libunistring-0:1.1 100% | 431.7 MiB/s |   1.7 MiB |  00m00s
[ 45/170] Installing libidn2-0:2.3.8-1. 100% |  60.6 MiB/s | 558.7 KiB |  00m00s
[ 46/170] Installing crypto-policies-0: 100% |  40.7 MiB/s | 166.6 KiB |  00m00s
[ 47/170] Installing dwz-0:0.15-9.fc42. 100% |  22.0 MiB/s | 292.4 KiB |  00m00s
[ 48/170] Installing mpfr-0:4.2.2-1.fc4 100% | 270.3 MiB/s | 830.4 KiB |  00m00s
[ 49/170] Installing gawk-0:5.3.2-1.fc4 100% | 106.8 MiB/s |   1.8 MiB |  00m00s
[ 50/170] Installing libksba-0:1.6.7-3. 100% | 395.6 MiB/s | 405.1 KiB |  00m00s
[ 51/170] Installing unzip-0:6.0-66.fc4 100% |  29.6 MiB/s | 393.8 KiB |  00m00s
[ 52/170] Installing file-libs-0:5.46-3 100% | 697.5 MiB/s |  11.9 MiB |  00m00s
[ 53/170] Installing file-0:5.46-3.fc43 100% |   8.3 MiB/s | 101.7 KiB |  00m00s
[ 54/170] Installing pcre2-0:10.45-1.fc 100% | 341.4 MiB/s | 699.1 KiB |  00m00s
[ 55/170] Installing grep-0:3.12-1.fc43 100% |  66.8 MiB/s |   1.0 MiB |  00m00s
[ 56/170] Installing xz-1:5.8.1-1.fc43. 100% |  83.2 MiB/s |   1.3 MiB |  00m00s
[ 57/170] Installing libeconf-0:0.7.6-1 100% |  64.7 MiB/s |  66.2 KiB |  00m00s
[ 58/170] Installing libcap-ng-0:0.8.5- 100% |  73.1 MiB/s |  74.8 KiB |  00m00s
[ 59/170] Installing audit-libs-0:4.0.4 100% | 345.0 MiB/s | 353.3 KiB |  00m00s
[ 60/170] Installing pam-libs-0:1.7.0-4 100% | 126.1 MiB/s | 129.1 KiB |  00m00s
[ 61/170] Installing libcap-0:2.76-1.fc 100% |  17.4 MiB/s | 214.3 KiB |  00m00s
[ 62/170] Installing systemd-libs-0:257 100% | 372.0 MiB/s |   2.2 MiB |  00m00s
[ 63/170] Installing libsmartcols-0:2.4 100% | 177.3 MiB/s | 181.5 KiB |  00m00s
[ 64/170] Installing lz4-libs-0:1.10.0- 100% | 154.7 MiB/s | 158.5 KiB |  00m00s
[ 65/170] Installing lua-libs-0:5.4.7-3 100% | 271.5 MiB/s | 278.1 KiB |  00m00s
[ 66/170] Installing json-c-0:0.18-2.fc 100% |   0.0   B/s |  88.0 KiB |  00m00s
[ 67/170] Installing libffi-0:3.4.8-1.f 100% |  82.4 MiB/s |  84.3 KiB |  00m00s
[ 68/170] Installing p11-kit-0:0.25.5-8 100% | 121.4 MiB/s |   2.2 MiB |  00m00s
[ 69/170] Installing libsepol-0:3.8-1.f 100% | 403.8 MiB/s | 827.0 KiB |  00m00s
[ 70/170] Installing libselinux-0:3.8-3 100% | 189.7 MiB/s | 194.3 KiB |  00m00s
[ 71/170] Installing findutils-1:4.10.0 100% | 117.1 MiB/s |   1.9 MiB |  00m00s
[ 72/170] Installing sed-0:4.9-4.fc42.x 100% |  60.4 MiB/s | 865.5 KiB |  00m00s
[ 73/170] Installing libmount-0:2.40.4- 100% | 349.0 MiB/s | 357.4 KiB |  00m00s
[ 74/170] Installing alternatives-0:1.3 100% |   5.7 MiB/s |  63.8 KiB |  00m00s
[ 75/170] Installing p11-kit-trust-0:0. 100% |  20.4 MiB/s | 397.1 KiB |  00m00s
[ 76/170] Installing util-linux-core-0: 100% |  83.9 MiB/s |   1.4 MiB |  00m00s
[ 77/170] Installing tar-2:1.35-5.fc42. 100% | 164.6 MiB/s |   3.0 MiB |  00m00s
[ 78/170] Installing libsemanage-0:3.8. 100% | 299.0 MiB/s | 306.2 KiB |  00m00s
[ 79/170] Installing systemd-standalone 100% |  22.6 MiB/s | 278.0 KiB |  00m00s
[ 80/170] Installing zstd-0:1.5.7-1.fc4 100% | 114.0 MiB/s |   1.7 MiB |  00m00s
[ 81/170] Installing libusb1-0:1.0.28-2 100% | 168.7 MiB/s | 172.7 KiB |  00m00s
[ 82/170] Installing zip-0:3.0-43.fc42. 100% |  52.8 MiB/s | 702.4 KiB |  00m00s
[ 83/170] Installing gnupg2-keyboxd-0:2 100% |  33.0 MiB/s | 202.7 KiB |  00m00s
[ 84/170] Installing libpsl-0:0.21.5-5. 100% |  75.7 MiB/s |  77.5 KiB |  00m00s
[ 85/170] Installing libfdisk-0:2.40.4- 100% | 364.7 MiB/s | 373.5 KiB |  00m00s
[ 86/170] Installing gnupg2-verify-0:2. 100% |  26.3 MiB/s | 349.9 KiB |  00m00s
[ 87/170] Installing nettle-0:3.10.1-1. 100% | 387.5 MiB/s | 793.6 KiB |  00m00s
[ 88/170] Installing gnutls-0:3.8.9-5.f 100% | 397.1 MiB/s |   3.6 MiB |  00m00s
[ 89/170] Installing libxml2-0:2.12.10- 100% | 113.1 MiB/s |   1.7 MiB |  00m00s
[ 90/170] Installing bzip2-0:1.0.8-20.f 100% |   8.5 MiB/s | 103.8 KiB |  00m00s
[ 91/170] Installing add-determinism-0: 100% | 145.1 MiB/s |   2.5 MiB |  00m00s
[ 92/170] Installing build-reproducibil 100% |   0.0   B/s |   1.0 KiB |  00m00s
[ 93/170] Installing cpio-0:2.15-2.fc41 100% |  78.6 MiB/s |   1.1 MiB |  00m00s
[ 94/170] Installing diffutils-0:3.12-2 100% | 104.1 MiB/s |   1.6 MiB |  00m00s
[ 95/170] Installing ed-0:1.21-2.fc42.x 100% |  12.1 MiB/s | 148.8 KiB |  00m00s
[ 96/170] Installing patch-0:2.8-1.fc43 100% |  18.6 MiB/s | 228.3 KiB |  00m00s
[ 97/170] Installing libgomp-0:15.1.1-2 100% | 527.8 MiB/s | 540.5 KiB |  00m00s
[ 98/170] Installing libtool-ltdl-0:2.5 100% |   0.0   B/s |  71.2 KiB |  00m00s
[ 99/170] Installing gdbm-libs-1:1.23-9 100% | 128.5 MiB/s | 131.6 KiB |  00m00s
[100/170] Installing cyrus-sasl-lib-0:2 100% | 144.0 MiB/s |   2.3 MiB |  00m00s
[101/170] Installing jansson-0:2.14-2.f 100% |  92.2 MiB/s |  94.4 KiB |  00m00s
[102/170] Installing libpkgconf-0:2.3.0 100% |   0.0   B/s |  79.2 KiB |  00m00s
[103/170] Installing pkgconf-0:2.3.0-2. 100% |   7.4 MiB/s |  91.0 KiB |  00m00s
[104/170] Installing pkgconf-pkg-config 100% | 161.2 KiB/s |   1.8 KiB |  00m00s
[105/170] Installing xxhash-libs-0:0.8. 100% |  89.4 MiB/s |  91.6 KiB |  00m00s
[106/170] Installing libnghttp2-0:1.65. 100% | 159.5 MiB/s | 163.3 KiB |  00m00s
[107/170] Installing keyutils-libs-0:1. 100% |   0.0   B/s |  59.7 KiB |  00m00s
[108/170] Installing libcom_err-0:1.47. 100% |   0.0   B/s |  68.2 KiB |  00m00s
[109/170] Installing libverto-0:0.3.2-1 100% |   0.0   B/s |  27.2 KiB |  00m00s
[110/170] Installing libbrotli-0:1.1.0- 100% | 408.0 MiB/s | 835.6 KiB |  00m00s
[111/170] Installing filesystem-srpm-ma 100% |   0.0   B/s |  38.9 KiB |  00m00s
[112/170] Installing elfutils-default-y 100% | 408.6 KiB/s |   2.0 KiB |  00m00s
[113/170] Installing elfutils-libs-0:0. 100% | 334.6 MiB/s | 685.2 KiB |  00m00s
[114/170] Installing rust-srpm-macros-0 100% |   0.0   B/s |   5.6 KiB |  00m00s
[115/170] Installing qt6-srpm-macros-0: 100% |   0.0   B/s | 740.0   B |  00m00s
[116/170] Installing qt5-srpm-macros-0: 100% |   0.0   B/s | 776.0   B |  00m00s
[117/170] Installing perl-srpm-macros-0 100% |   0.0   B/s |   1.1 KiB |  00m00s
[118/170] Installing package-notes-srpm 100% |   0.0   B/s |   2.0 KiB |  00m00s
[119/170] Installing openblas-srpm-macr 100% |   0.0   B/s | 392.0   B |  00m00s
[120/170] Installing ocaml-srpm-macros- 100% |   0.0   B/s |   2.2 KiB |  00m00s
[121/170] Installing kernel-srpm-macros 100% |   0.0   B/s |   2.3 KiB |  00m00s
[122/170] Installing gnat-srpm-macros-0 100% |   0.0   B/s |   1.3 KiB |  00m00s
[123/170] Installing ghc-srpm-macros-0: 100% |   0.0   B/s |   1.0 KiB |  00m00s
[124/170] Installing fpc-srpm-macros-0: 100% |   0.0   B/s | 420.0   B |  00m00s
[125/170] Installing ansible-srpm-macro 100% |  35.4 MiB/s |  36.2 KiB |  00m00s
[126/170] Installing coreutils-common-0 100% | 418.2 MiB/s |  11.3 MiB |  00m00s
[127/170] Installing openssl-libs-1:3.5 100% | 467.8 MiB/s |   8.9 MiB |  00m00s
[128/170] Installing coreutils-0:9.7-3. 100% | 175.7 MiB/s |   5.4 MiB |  00m00s
[129/170] Installing ca-certificates-0: 100% |   2.2 MiB/s |   2.4 MiB |  00m01s
[130/170] Installing libarchive-0:3.7.7 100% | 303.6 MiB/s | 932.6 KiB |  00m00s
[131/170] Installing krb5-libs-0:1.21.3 100% | 164.3 MiB/s |   2.3 MiB |  00m00s
>>> Running sysusers scriptlet: tpm2-tss-0:4.1.3-7.fc43.x86_64                  
>>> Finished sysusers scriptlet: tpm2-tss-0:4.1.3-7.fc43.x86_64                 
>>> Scriptlet output:                                                           
>>> Creating group 'tss' with GID 59.                                           
>>> Creating user 'tss' (Account used for TPM access) with UID 59 and GID 59.   
>>>                                                                             
[132/170] Installing tpm2-tss-0:4.1.3-7 100% | 313.6 MiB/s |   1.6 MiB |  00m00s
[133/170] Installing ima-evm-utils-libs 100% |  60.5 MiB/s |  62.0 KiB |  00m00s
[134/170] Installing gnupg2-gpg-agent-0 100% |  33.0 MiB/s | 675.4 KiB |  00m00s
[135/170] Installing libssh-0:0.11.1-4. 100% | 277.1 MiB/s | 567.5 KiB |  00m00s
[136/170] Installing gzip-0:1.13-3.fc42 100% |  29.9 MiB/s | 398.4 KiB |  00m00s
[137/170] Installing rpm-sequoia-0:1.8. 100% | 417.3 MiB/s |   2.5 MiB |  00m00s
[138/170] Installing rpm-libs-0:5.99.90 100% | 303.2 MiB/s | 931.3 KiB |  00m00s
[139/170] Installing libfsverity-0:1.6- 100% |   0.0   B/s |  33.5 KiB |  00m00s
[140/170] Installing libevent-0:2.1.12- 100% | 295.2 MiB/s | 906.9 KiB |  00m00s
[141/170] Installing openldap-0:2.6.9-5 100% | 321.7 MiB/s | 658.9 KiB |  00m00s
[142/170] Installing libcurl-0:8.14.0-1 100% | 437.7 MiB/s | 896.4 KiB |  00m00s
[143/170] Installing elfutils-debuginfo 100% |   7.0 MiB/s |  86.2 KiB |  00m00s
[144/170] Installing elfutils-0:0.193-2 100% | 162.4 MiB/s |   2.9 MiB |  00m00s
[145/170] Installing binutils-0:2.44-3. 100% | 354.8 MiB/s |  25.9 MiB |  00m00s
[146/170] Installing gdb-minimal-0:16.3 100% | 308.1 MiB/s |  13.2 MiB |  00m00s
[147/170] Installing debugedit-0:5.1-6. 100% |  15.9 MiB/s | 195.4 KiB |  00m00s
[148/170] Installing curl-0:8.14.0-1.fc 100% |  23.1 MiB/s | 472.6 KiB |  00m00s
[149/170] Installing rpm-0:5.99.90-5.fc 100% |  83.6 MiB/s |   2.5 MiB |  00m00s
[150/170] Installing efi-srpm-macros-0: 100% |  40.2 MiB/s |  41.1 KiB |  00m00s
[151/170] Installing java-srpm-macros-0 100% |   0.0   B/s | 380.0   B |  00m00s
[152/170] Installing lua-srpm-macros-0: 100% |   0.0   B/s |   1.9 KiB |  00m00s
[153/170] Installing tree-sitter-srpm-m 100% |   0.0   B/s |   8.6 KiB |  00m00s
[154/170] Installing zig-srpm-macros-0: 100% |   0.0   B/s |   1.7 KiB |  00m00s
[155/170] Installing gnupg2-dirmngr-0:2 100% |  31.9 MiB/s | 621.1 KiB |  00m00s
[156/170] Installing gnupg2-0:2.4.8-2.f 100% | 242.6 MiB/s |   6.6 MiB |  00m00s
[157/170] Installing rpm-sign-libs-0:5. 100% |  39.6 MiB/s |  40.5 KiB |  00m00s
[158/170] Installing rpm-build-libs-0:5 100% | 259.0 MiB/s | 265.2 KiB |  00m00s
[159/170] Installing gpgverify-0:2.1-3. 100% |   0.0   B/s |   9.4 KiB |  00m00s
[160/170] Installing rpm-build-0:5.99.9 100% |  21.8 MiB/s | 290.3 KiB |  00m00s
[161/170] Installing pyproject-srpm-mac 100% |   0.0   B/s |   2.5 KiB |  00m00s
[162/170] Installing redhat-rpm-config- 100% |  91.7 MiB/s | 187.8 KiB |  00m00s
[163/170] Installing forge-srpm-macros- 100% |   0.0   B/s |  40.3 KiB |  00m00s
[164/170] Installing fonts-srpm-macros- 100% |   0.0   B/s |  57.0 KiB |  00m00s
[165/170] Installing go-srpm-macros-0:3 100% |   0.0   B/s |  62.0 KiB |  00m00s
[166/170] Installing python-srpm-macros 100% |   0.0   B/s |  53.0 KiB |  00m00s
[167/170] Installing which-0:2.23-1.fc4 100% |   7.0 MiB/s |  85.6 KiB |  00m00s
[168/170] Installing util-linux-0:2.40. 100% | 108.2 MiB/s |   3.5 MiB |  00m00s
[169/170] Installing shadow-utils-2:4.1 100% | 144.8 MiB/s |   4.1 MiB |  00m00s
[170/170] Installing info-0:7.2-3.fc42. 100% | 246.2 KiB/s | 358.3 KiB |  00m01s
Warning: skipped OpenPGP checks for 6 packages from repository: copr_base
Complete!
Finish: installing minimal buildroot with dnf5
Start: creating root cache
Finish: creating root cache
Finish: chroot init
INFO: Installed packages:
INFO: add-determinism-0.6.0-1.fc43.x86_64
alternatives-1.33-1.fc43.x86_64
ansible-srpm-macros-1-17.1.fc42.noarch
audit-libs-4.0.4-2.fc43.x86_64
bash-5.2.37-3.fc43.x86_64
binutils-2.44-3.fc43.x86_64
build-reproducibility-srpm-macros-0.6.0-1.fc43.noarch
bzip2-1.0.8-20.fc42.x86_64
bzip2-libs-1.0.8-20.fc42.x86_64
ca-certificates-2024.2.69_v8.0.401-5.fc42.noarch
coreutils-9.7-3.fc43.x86_64
coreutils-common-9.7-3.fc43.x86_64
cpio-2.15-2.fc41.x86_64
crypto-policies-20250402-2.git86c0178.fc43.noarch
curl-8.14.0-1.fc43.x86_64
cyrus-sasl-lib-2.1.28-30.fc42.x86_64
debugedit-5.1-6.fc43.x86_64
diffutils-3.12-2.fc43.x86_64
dwz-0.15-9.fc42.x86_64
ed-1.21-2.fc42.x86_64
efi-srpm-macros-6-3.fc43.noarch
elfutils-0.193-2.fc43.x86_64
elfutils-debuginfod-client-0.193-2.fc43.x86_64
elfutils-default-yama-scope-0.193-2.fc43.noarch
elfutils-libelf-0.193-2.fc43.x86_64
elfutils-libs-0.193-2.fc43.x86_64
fedora-gpg-keys-43-0.2.noarch
fedora-release-43-0.16.noarch
fedora-release-common-43-0.16.noarch
fedora-release-identity-basic-43-0.16.noarch
fedora-repos-43-0.2.noarch
fedora-repos-rawhide-43-0.2.noarch
file-5.46-3.fc43.x86_64
file-libs-5.46-3.fc43.x86_64
filesystem-3.18-44.fc43.x86_64
filesystem-srpm-macros-3.18-44.fc43.noarch
findutils-4.10.0-5.fc42.x86_64
fonts-srpm-macros-2.0.5-22.fc43.noarch
forge-srpm-macros-0.4.0-2.fc42.noarch
fpc-srpm-macros-1.3-14.fc42.noarch
gawk-5.3.2-1.fc43.x86_64
gdb-minimal-16.3-1.fc43.x86_64
gdbm-libs-1.23-9.fc42.x86_64
ghc-srpm-macros-1.9.2-2.fc42.noarch
glibc-2.41.9000-15.fc43.x86_64
glibc-common-2.41.9000-15.fc43.x86_64
glibc-gconv-extra-2.41.9000-15.fc43.x86_64
glibc-minimal-langpack-2.41.9000-15.fc43.x86_64
gmp-6.3.0-3.fc43.x86_64
gnat-srpm-macros-6-7.fc42.noarch
gnupg2-2.4.8-2.fc43.x86_64
gnupg2-dirmngr-2.4.8-2.fc43.x86_64
gnupg2-gpg-agent-2.4.8-2.fc43.x86_64
gnupg2-gpgconf-2.4.8-2.fc43.x86_64
gnupg2-keyboxd-2.4.8-2.fc43.x86_64
gnupg2-verify-2.4.8-2.fc43.x86_64
gnutls-3.8.9-5.fc43.x86_64
go-srpm-macros-3.6.0-7.fc43.noarch
gpg-pubkey-36f612dcf27f7d1a48a835e4dbfcf71c6d9f90a6-6786af3b
gpg-pubkey-b0f4950458f69e1150c6c5edc8ac4916105ef944-65ca83d1
gpg-pubkey-c6e7f081cf80e13146676e88829b606631645531-66b6dccf
gpgverify-2.1-3.fc43.noarch
grep-3.12-1.fc43.x86_64
gzip-1.13-3.fc42.x86_64
ima-evm-utils-libs-1.6.2-5.fc43.x86_64
info-7.2-3.fc42.x86_64
jansson-2.14-2.fc42.x86_64
java-srpm-macros-1-3.fc43.noarch
json-c-0.18-2.fc42.x86_64
kernel-srpm-macros-1.0-25.fc42.noarch
keyutils-libs-1.6.3-5.fc42.x86_64
krb5-libs-1.21.3-5.fc42.x86_64
libacl-2.3.2-3.fc42.x86_64
libarchive-3.7.7-4.fc43.x86_64
libassuan-2.5.7-3.fc42.x86_64
libattr-2.5.2-5.fc42.x86_64
libblkid-2.40.4-7.fc43.x86_64
libbrotli-1.1.0-7.fc43.x86_64
libcap-2.76-1.fc43.x86_64
libcap-ng-0.8.5-4.fc42.x86_64
libcom_err-1.47.2-3.fc42.x86_64
libcurl-8.14.0-1.fc43.x86_64
libeconf-0.7.6-1.fc43.x86_64
libevent-2.1.12-15.fc42.x86_64
libfdisk-2.40.4-7.fc43.x86_64
libffi-3.4.8-1.fc43.x86_64
libfsverity-1.6-2.fc42.x86_64
libgcc-15.1.1-2.fc43.x86_64
libgcrypt-1.11.1-1.fc43.x86_64
libgomp-15.1.1-2.fc43.x86_64
libgpg-error-1.55-1.fc43.x86_64
libidn2-2.3.8-1.fc43.x86_64
libksba-1.6.7-3.fc42.x86_64
libmount-2.40.4-7.fc43.x86_64
libnghttp2-1.65.0-1.fc43.x86_64
libpkgconf-2.3.0-2.fc42.x86_64
libpsl-0.21.5-5.fc42.x86_64
libselinux-3.8-3.fc43.x86_64
libsemanage-3.8.1-2.fc43.x86_64
libsepol-3.8-1.fc42.x86_64
libsmartcols-2.40.4-7.fc43.x86_64
libssh-0.11.1-4.fc42.x86_64
libssh-config-0.11.1-4.fc42.noarch
libstdc++-15.1.1-2.fc43.x86_64
libtasn1-4.20.0-1.fc43.x86_64
libtool-ltdl-2.5.4-4.fc42.x86_64
libunistring-1.1-9.fc42.x86_64
libusb1-1.0.28-2.fc43.x86_64
libuuid-2.40.4-7.fc43.x86_64
libverto-0.3.2-10.fc42.x86_64
libxcrypt-4.4.38-7.fc43.x86_64
libxml2-2.12.10-1.fc43.x86_64
libzstd-1.5.7-1.fc43.x86_64
lua-libs-5.4.7-3.fc43.x86_64
lua-srpm-macros-1-15.fc42.noarch
lz4-libs-1.10.0-2.fc42.x86_64
mpfr-4.2.2-1.fc43.x86_64
ncurses-base-6.5-5.20250125.fc42.noarch
ncurses-libs-6.5-5.20250125.fc42.x86_64
nettle-3.10.1-1.fc43.x86_64
npth-1.8-2.fc42.x86_64
ocaml-srpm-macros-10-4.fc42.noarch
openblas-srpm-macros-2-19.fc42.noarch
openldap-2.6.9-5.fc43.x86_64
openssl-libs-3.5.0-3.fc43.x86_64
p11-kit-0.25.5-8.fc43.x86_64
p11-kit-trust-0.25.5-8.fc43.x86_64
package-notes-srpm-macros-0.5-13.fc42.noarch
pam-libs-1.7.0-4.fc42.x86_64
patch-2.8-1.fc43.x86_64
pcre2-10.45-1.fc43.x86_64
pcre2-syntax-10.45-1.fc43.noarch
perl-srpm-macros-1-57.fc42.noarch
pkgconf-2.3.0-2.fc42.x86_64
pkgconf-m4-2.3.0-2.fc42.noarch
pkgconf-pkg-config-2.3.0-2.fc42.x86_64
popt-1.19-8.fc42.x86_64
publicsuffix-list-dafsa-20250116-1.fc42.noarch
pyproject-srpm-macros-1.18.1-1.fc43.noarch
python-srpm-macros-3.13-5.fc43.noarch
qt5-srpm-macros-5.15.17-1.fc43.noarch
qt6-srpm-macros-6.9.0-2.fc43.noarch
readline-8.2-13.fc43.x86_64
redhat-rpm-config-343-6.fc43.noarch
rpm-5.99.90-5.fc43.x86_64
rpm-build-5.99.90-5.fc43.x86_64
rpm-build-libs-5.99.90-5.fc43.x86_64
rpm-libs-5.99.90-5.fc43.x86_64
rpm-sequoia-1.8.0-1.fc43.x86_64
rpm-sign-libs-5.99.90-5.fc43.x86_64
rust-srpm-macros-26.3-4.fc42.noarch
sed-4.9-4.fc42.x86_64
setup-2.15.0-25.fc43.noarch
shadow-utils-4.17.4-1.fc43.x86_64
sqlite-libs-3.49.2-1.fc43.x86_64
systemd-libs-257.6-1.fc43.x86_64
systemd-standalone-sysusers-257.6-1.fc43.x86_64
tar-1.35-5.fc42.x86_64
tpm2-tss-4.1.3-7.fc43.x86_64
tree-sitter-srpm-macros-0.2.4-1.fc43.noarch
unzip-6.0-66.fc42.x86_64
util-linux-2.40.4-7.fc43.x86_64
util-linux-core-2.40.4-7.fc43.x86_64
which-2.23-1.fc42.x86_64
xxhash-libs-0.8.3-2.fc42.x86_64
xz-5.8.1-1.fc43.x86_64
xz-libs-5.8.1-1.fc43.x86_64
zig-srpm-macros-1-4.fc42.noarch
zip-3.0-43.fc42.x86_64
zlib-ng-compat-2.2.4-2.fc43.x86_64
zstd-1.5.7-1.fc43.x86_64
Start: buildsrpm
Start: rpmbuild -bs
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.src.rpm
Finish: rpmbuild -bs
INFO: chroot_scan: 1 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-rawhide-x86_64-1748943842.640973/root/var/log/dnf5.log
INFO: chroot_scan: creating tarball /var/lib/copr-rpmbuild/results/chroot_scan.tar.gz
/bin/tar: Removing leading `/' from member names
Finish: buildsrpm
INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-lhllgb2w/python-django4.2/python-django4.2.spec) Config(child) 0 minutes 16 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
INFO: Start(/var/lib/copr-rpmbuild/results/python-django4.2-4.2.20-2.fc43.src.rpm)  Config(fedora-rawhide-x86_64)
Start(bootstrap): chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1748943842.640973/root.
INFO: reusing tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1748943842.640973/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
Finish(bootstrap): chroot init
Start: chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1748943842.640973/root.
INFO: calling preinit hooks
INFO: enabled root cache
Start: unpacking root cache
Finish: unpacking root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Buildroot is handled by package management downloaded with a bootstrap image:
  rpm-5.99.90-5.fc43.x86_64
  rpm-sequoia-1.8.0-1.fc43.x86_64
  dnf5-5.2.13.1-2.fc43.x86_64
  dnf5-plugins-5.2.13.1-2.fc43.x86_64
Finish: chroot init
Start: build phase for python-django4.2-4.2.20-2.fc43.src.rpm
Start: build setup for python-django4.2-4.2.20-2.fc43.src.rpm
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.src.rpm
Updating and loading repositories:
 fedora                                 100% | 173.3 KiB/s |  27.2 KiB |  00m00s
 Copr repository                        100% | 352.0   B/s |   1.5 KiB |  00m04s
Repositories loaded.
Package                 Arch   Version         Repository      Size
Installing:
 bash-completion        noarch 1:2.16-1.fc42   fedora       1.4 MiB
 make                   x86_64 1:4.4.1-10.fc42 fedora       1.8 MiB
 python3-asgiref        noarch 3.8.1-2.fc43    copr_base  150.2 KiB
 python3-devel          x86_64 3.13.3-3.fc43   fedora       1.8 MiB
Installing dependencies:
 expat                  x86_64 2.7.1-1.fc43    fedora     294.2 KiB
 libb2                  x86_64 0.98.1-13.fc42  fedora      46.1 KiB
 mpdecimal              x86_64 4.0.1-1.fc43    fedora     217.2 KiB
 pyproject-rpm-macros   noarch 1.18.1-1.fc43   copr_base  114.5 KiB
 python-pip-wheel       noarch 25.1.1-4.fc43   copr_base    1.2 MiB
 python-rpm-macros      noarch 3.13-5.fc43     fedora      22.1 KiB
 python3                x86_64 3.13.3-3.fc43   fedora      28.7 KiB
 python3-libs           x86_64 3.13.3-3.fc43   fedora      39.9 MiB
 python3-packaging      noarch 25.0-1.fc43     fedora     563.4 KiB
 python3-rpm-generators noarch 14-12.fc42      fedora      81.7 KiB
 python3-rpm-macros     noarch 3.13-5.fc43     fedora       6.4 KiB
 tzdata                 noarch 2025b-1.fc43    fedora       1.6 MiB

Transaction Summary:
 Installing:        16 packages

Total size of inbound packages is 13 MiB. Need to download 13 MiB.
After this operation, 49 MiB extra will be used (install 49 MiB, remove 0 B).
[ 1/16] make-1:4.4.1-10.fc42.x86_64     100% |  52.1 MiB/s | 587.0 KiB |  00m00s
[ 2/16] bash-completion-1:2.16-1.fc42.n 100% |  32.9 MiB/s | 471.5 KiB |  00m00s
[ 3/16] python3-devel-0:3.13.3-3.fc43.x 100% | 131.8 MiB/s | 404.8 KiB |  00m00s
[ 4/16] expat-0:2.7.1-1.fc43.x86_64     100% |  18.9 MiB/s | 115.9 KiB |  00m00s
[ 5/16] libb2-0:0.98.1-13.fc42.x86_64   100% |   3.5 MiB/s |  25.4 KiB |  00m00s
[ 6/16] python3-libs-0:3.13.3-3.fc43.x8 100% | 366.5 MiB/s |   9.2 MiB |  00m00s
[ 7/16] mpdecimal-0:4.0.1-1.fc43.x86_64 100% |   8.6 MiB/s |  97.1 KiB |  00m00s
[ 8/16] python3-0:3.13.3-3.fc43.x86_64  100% |  29.1 MiB/s |  29.8 KiB |  00m00s
[ 9/16] tzdata-0:2025b-1.fc43.noarch    100% | 232.4 MiB/s | 714.0 KiB |  00m00s
[10/16] python-rpm-macros-0:3.13-5.fc43 100% |  16.4 MiB/s |  16.8 KiB |  00m00s
[11/16] python3-rpm-generators-0:14-12. 100% |  28.5 MiB/s |  29.2 KiB |  00m00s
[12/16] python-pip-wheel-0:25.1.1-4.fc4 100% | 241.0 MiB/s |   1.2 MiB |  00m00s
[13/16] python3-rpm-macros-0:3.13-5.fc4 100% |  11.3 MiB/s |  11.5 KiB |  00m00s
[14/16] pyproject-rpm-macros-0:1.18.1-1 100% |  44.4 MiB/s |  45.4 KiB |  00m00s
[15/16] python3-packaging-0:25.0-1.fc43 100% | 152.0 MiB/s | 155.7 KiB |  00m00s
[16/16] python3-asgiref-0:3.8.1-2.fc43. 100% |  47.9 KiB/s |  57.6 KiB |  00m01s
--------------------------------------------------------------------------------
[16/16] Total                           100% |  10.3 MiB/s |  13.1 MiB |  00m01s
Running transaction
[ 1/18] Verify package files            100% | 888.0   B/s |  16.0   B |  00m00s
[ 2/18] Prepare transaction             100% | 516.0   B/s |  16.0   B |  00m00s
[ 3/18] Installing python-rpm-macros-0: 100% |   0.0   B/s |  22.8 KiB |  00m00s
[ 4/18] Installing python3-rpm-macros-0 100% |   0.0   B/s |   6.7 KiB |  00m00s
[ 5/18] Installing pyproject-rpm-macros 100% | 113.7 MiB/s | 116.4 KiB |  00m00s
[ 6/18] Installing python-pip-wheel-0:2 100% | 249.0 MiB/s |   1.2 MiB |  00m00s
[ 7/18] Installing tzdata-0:2025b-1.fc4 100% |  63.1 MiB/s |   1.9 MiB |  00m00s
[ 8/18] Installing mpdecimal-0:4.0.1-1. 100% | 213.7 MiB/s | 218.8 KiB |  00m00s
[ 9/18] Installing libb2-0:0.98.1-13.fc 100% |   0.0   B/s |  47.2 KiB |  00m00s
[10/18] Installing expat-0:2.7.1-1.fc43 100% |  16.1 MiB/s | 296.3 KiB |  00m00s
[11/18] Installing python3-libs-0:3.13. 100% | 353.4 MiB/s |  40.3 MiB |  00m00s
[12/18] Installing python3-0:3.13.3-3.f 100% |   2.5 MiB/s |  30.4 KiB |  00m00s
[13/18] Installing python3-packaging-0: 100% | 281.2 MiB/s | 575.9 KiB |  00m00s
[14/18] Installing python3-rpm-generato 100% |  81.0 MiB/s |  82.9 KiB |  00m00s
[15/18] Installing python3-devel-0:3.13 100% |  95.9 MiB/s |   1.8 MiB |  00m00s
[16/18] Installing python3-asgiref-0:3. 100% | 154.1 MiB/s | 157.8 KiB |  00m00s
[17/18] Installing make-1:4.4.1-10.fc42 100% | 105.9 MiB/s |   1.8 MiB |  00m00s
[18/18] Installing bash-completion-1:2. 100% |  31.1 MiB/s |   1.5 MiB |  00m00s
Warning: skipped OpenPGP checks for 3 packages from repository: copr_base
Complete!
Finish: build setup for python-django4.2-4.2.20-2.fc43.src.rpm
Start: rpmbuild python-django4.2-4.2.20-2.fc43.src.rpm
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.CPZYrl
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.1o0ytQ
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ rm -rf Django-4.2.20
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/Django-4.2.20.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd Django-4.2.20
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/backport-3426a5c33c36266af42128ee9eca4921e68ea876.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/Django-skip-flaky-unicode-tests.diff
+ pushd django
~/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/django ~/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20
+ for file in conf/project_template/manage.py-tpl
+ sed -i 's/\/env python/\/python3/' conf/project_template/manage.py-tpl
+ popd
~/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20
+ sed -i 's/psycopg\[binary\]>=3\.1\.8/psycopg>=3.1.8/' tests/requirements/postgres.txt
+ sed -i '/^pywatchman\b/d' tests/requirements/py3.txt
+ sed -i '/^tzdata$/d' tests/requirements/py3.txt
+ sed -i '/^black\b/d' tests/requirements/py3.txt
+ sed -i '/^black\b/d' docs/requirements.txt
+ sed -i '/^blacken-docs\b/d' docs/requirements.txt
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.0SMmQI
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(packaging)'
+ echo 'python3dist(pip) >= 19'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ VALAFLAGS=-g
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ CC=gcc
+ CXX=g++
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ RPM_TOXENV=py313
+ FEDORA=43
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir --output /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires -r docs/requirements.txt
Handling pyenchant from requirements file docs/requirements.txt
Requirement not satisfied: pyenchant
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement not satisfied: Sphinx>=4.5.0
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement not satisfied: sphinxcontrib-spelling
Exiting dependency generation pass: all requirements files
+ cat /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires
+ rm -rfv '*.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
 fedora                                 100% | 299.0 KiB/s |  27.2 KiB |  00m00s
 Copr repository                        100% |  11.9 KiB/s |   1.5 KiB |  00m00s
Repositories loaded.
Package "bash-completion-1:2.16-1.fc42.noarch" is already installed.
Package "make-1:4.4.1-10.fc42.x86_64" is already installed.
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-asgiref-3.8.1-2.fc43.noarch" is already installed.
Package "python3-devel-3.13.3-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-1.fc43.noarch" is already installed.

Package                         Arch   Version                 Repository      Size
Installing:
 python3-enchant                noarch 3.2.2-16.fc43           copr_base  367.2 KiB
 python3-pip                    noarch 25.1.1-4.fc43           copr_base   11.5 MiB
 python3-sphinx                 noarch 1:8.2.3-5.fc43          fedora      11.4 MiB
 python3-sphinxcontrib-spelling noarch 7.3.3-12.fc43           copr_base   64.3 KiB
Installing dependencies:
 enchant2                       x86_64 2.8.6-1.fc43            fedora     203.3 KiB
 glib2                          x86_64 2.85.0-1.fc43           fedora      14.7 MiB
 hunspell                       x86_64 1.7.2-9.fc42            fedora       1.4 MiB
 hunspell-en-US                 noarch 0.20201207-11.fc42      fedora     557.4 KiB
 hunspell-filesystem            x86_64 1.7.2-9.fc42            fedora       0.0   B
 python3-babel                  noarch 2.17.0-2.fc43~bootstrap copr_base   30.2 MiB
 python3-charset-normalizer     noarch 3.4.2-1.fc43            copr_base  330.1 KiB
 python3-docutils               noarch 0.21.2-2.fc42           fedora       4.9 MiB
 python3-idna                   noarch 3.10-2.fc42             fedora     628.0 KiB
 python3-imagesize              noarch 1.4.1-11.fc43           copr_base   35.4 KiB
 python3-jinja2                 noarch 3.1.6-1.fc43            fedora       2.9 MiB
 python3-markupsafe             x86_64 3.0.2-2.fc43            copr_base   55.9 KiB
 python3-pygments               noarch 2.19.1-1.fc43           fedora      10.8 MiB
 python3-requests               noarch 2.32.3-13.fc43          copr_base  483.4 KiB
 python3-roman-numerals-py      noarch 3.1.0-1.fc43            fedora      38.7 KiB
 python3-snowballstemmer        noarch 3.0.1-4.fc43            copr_base    1.8 MiB
 python3-sphinx-theme-alabaster noarch 0.7.16-6.fc41           fedora      41.9 KiB
 python3-urllib3                noarch 2.4.0-2.fc43            fedora       1.0 MiB

Transaction Summary:
 Installing:        22 packages

Total size of inbound packages is 21 MiB. Need to download 21 MiB.
After this operation, 93 MiB extra will be used (install 93 MiB, remove 0 B).
[ 1/22] python3-pip-0:25.1.1-4.fc43.noa 100% | 131.6 MiB/s |   2.5 MiB |  00m00s
[ 2/22] python3-sphinx-1:8.2.3-5.fc43.n 100% | 120.8 MiB/s |   2.8 MiB |  00m00s
[ 3/22] python3-docutils-0:0.21.2-2.fc4 100% |  90.8 MiB/s |   1.1 MiB |  00m00s
[ 4/22] python3-jinja2-0:3.1.6-1.fc43.n 100% | 121.2 MiB/s | 496.3 KiB |  00m00s
[ 5/22] python3-pygments-0:2.19.1-1.fc4 100% | 171.4 MiB/s |   2.6 MiB |  00m00s
[ 6/22] python3-roman-numerals-py-0:3.1 100% |   9.4 MiB/s |  19.3 KiB |  00m00s
[ 7/22] python3-sphinx-theme-alabaster- 100% |  11.8 MiB/s |  24.3 KiB |  00m00s
[ 8/22] enchant2-0:2.8.6-1.fc43.x86_64  100% |  26.4 MiB/s |  81.0 KiB |  00m00s
[ 9/22] glib2-0:2.85.0-1.fc43.x86_64    100% | 306.9 MiB/s |   3.1 MiB |  00m00s
[10/22] hunspell-0:1.7.2-9.fc42.x86_64  100% | 116.7 MiB/s | 478.1 KiB |  00m00s
[11/22] hunspell-en-US-0:0.20201207-11. 100% |  44.1 MiB/s | 180.7 KiB |  00m00s
[12/22] hunspell-filesystem-0:1.7.2-9.f 100% | 457.8 KiB/s |   7.8 KiB |  00m00s
[13/22] python3-babel-0:2.17.0-2.fc43~b 100% | 354.8 MiB/s |   6.7 MiB |  00m00s
[14/22] python3-imagesize-0:1.4.1-11.fc 100% |  22.0 MiB/s |  22.6 KiB |  00m00s
[15/22] python3-requests-0:2.32.3-13.fc 100% |  73.1 MiB/s | 149.7 KiB |  00m00s
[16/22] python3-idna-0:3.10-2.fc42.noar 100% |  57.3 MiB/s | 117.3 KiB |  00m00s
[17/22] python3-urllib3-0:2.4.0-2.fc43. 100% |  92.5 MiB/s | 284.2 KiB |  00m00s
[18/22] python3-snowballstemmer-0:3.0.1 100% |  85.9 MiB/s | 263.9 KiB |  00m00s
[19/22] python3-markupsafe-0:3.0.2-2.fc 100% |  30.4 MiB/s |  31.1 KiB |  00m00s
[20/22] python3-charset-normalizer-0:3. 100% |  51.4 MiB/s | 105.4 KiB |  00m00s
[21/22] python3-sphinxcontrib-spelling- 100% |  27.0 KiB/s |  35.1 KiB |  00m01s
[22/22] python3-enchant-0:3.2.2-16.fc43 100% |  50.4 KiB/s |  96.2 KiB |  00m02s
--------------------------------------------------------------------------------
[22/22] Total                           100% |  10.2 MiB/s |  21.1 MiB |  00m02s
Running transaction
[ 1/24] Verify package files            100% | 647.0   B/s |  22.0   B |  00m00s
[ 2/24] Prepare transaction             100% | 550.0   B/s |  22.0   B |  00m00s
[ 3/24] Installing python3-idna-0:3.10- 100% | 309.7 MiB/s | 634.3 KiB |  00m00s
[ 4/24] Installing hunspell-filesystem- 100% |   0.0   B/s | 388.0   B |  00m00s
[ 5/24] Installing hunspell-en-US-0:0.2 100% | 272.5 MiB/s | 558.1 KiB |  00m00s
[ 6/24] Installing hunspell-0:1.7.2-9.f 100% |  76.1 MiB/s |   1.4 MiB |  00m00s
[ 7/24] Installing python3-urllib3-0:2. 100% | 255.3 MiB/s |   1.0 MiB |  00m00s
[ 8/24] Installing python3-charset-norm 100% |  25.6 MiB/s | 340.2 KiB |  00m00s
[ 9/24] Installing python3-requests-0:2 100% | 242.0 MiB/s | 495.7 KiB |  00m00s
[10/24] Installing python3-markupsafe-0 100% |  58.7 MiB/s |  60.1 KiB |  00m00s
[11/24] Installing python3-jinja2-0:3.1 100% | 364.2 MiB/s |   2.9 MiB |  00m00s
[12/24] Installing python3-snowballstem 100% | 367.6 MiB/s |   1.8 MiB |  00m00s
[13/24] Installing python3-imagesize-0: 100% |  18.8 MiB/s |  38.5 KiB |  00m00s
[14/24] Installing python3-babel-0:2.17 100% | 357.7 MiB/s |  30.4 MiB |  00m00s
[15/24] Installing glib2-0:2.85.0-1.fc4 100% | 320.0 MiB/s |  14.7 MiB |  00m00s
[16/24] Installing enchant2-0:2.8.6-1.f 100% |  15.6 MiB/s | 207.0 KiB |  00m00s
[17/24] Installing python3-enchant-0:3. 100% | 183.6 MiB/s | 376.1 KiB |  00m00s
[18/24] Installing python3-sphinx-theme 100% |  45.3 MiB/s |  46.4 KiB |  00m00s
[19/24] Installing python3-roman-numera 100% |  13.6 MiB/s |  41.6 KiB |  00m00s
[20/24] Installing python3-pygments-0:2 100% | 229.9 MiB/s |  11.0 MiB |  00m00s
[21/24] Installing python3-docutils-0:0 100% | 155.9 MiB/s |   5.0 MiB |  00m00s
[22/24] Installing python3-sphinx-1:8.2 100% | 207.3 MiB/s |  11.6 MiB |  00m00s
[23/24] Installing python3-sphinxcontri 100% |  23.2 MiB/s |  71.3 KiB |  00m00s
[24/24] Installing python3-pip-0:25.1.1 100% | 142.0 MiB/s |  11.8 MiB |  00m00s
Warning: skipped OpenPGP checks for 9 packages from repository: copr_base
Complete!
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.XX5nUa
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(packaging)'
+ echo 'python3dist(pip) >= 19'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ VALAFLAGS=-g
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ CC=gcc
+ CXX=g++
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ RPM_TOXENV=py313
+ FEDORA=43
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir --output /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires -r docs/requirements.txt
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
   (installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
   (installed: Sphinx 8.2.3)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
   (installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement not satisfied: setuptools>=40.8.0
Exiting dependency generation pass: build backend
+ cat /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires
+ rm -rfv '*.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
 fedora                                 100% | 259.1 KiB/s |  27.2 KiB |  00m00s
 Copr repository                        100% |   1.1 KiB/s |   1.5 KiB |  00m01s
Repositories loaded.
Package "bash-completion-1:2.16-1.fc42.noarch" is already installed.
Package "make-1:4.4.1-10.fc42.x86_64" is already installed.
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-asgiref-3.8.1-2.fc43.noarch" is already installed.
Package "python3-devel-3.13.3-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-1.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-enchant-3.2.2-16.fc43.noarch" is already installed.
Package "python3-sphinx-1:8.2.3-5.fc43.noarch" is already installed.
Package "python3-sphinxcontrib-spelling-7.3.3-12.fc43.noarch" is already installed.

Package             Arch   Version       Repository      Size
Installing:
 python3-setuptools noarch 78.1.1-1.fc43 fedora       8.6 MiB

Transaction Summary:
 Installing:         1 package

Total size of inbound packages is 2 MiB. Need to download 2 MiB.
After this operation, 9 MiB extra will be used (install 9 MiB, remove 0 B).
[1/1] python3-setuptools-0:78.1.1-1.fc4 100% | 132.8 MiB/s |   2.0 MiB |  00m00s
--------------------------------------------------------------------------------
[1/1] Total                             100% |  27.3 MiB/s |   2.0 MiB |  00m00s
Running transaction
[1/3] Verify package files              100% | 500.0   B/s |   1.0   B |  00m00s
[2/3] Prepare transaction               100% |  76.0   B/s |   1.0   B |  00m00s
[3/3] Installing python3-setuptools-0:7 100% | 186.5 MiB/s |   8.8 MiB |  00m00s
Complete!
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.GVMg27
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(packaging)'
+ echo 'python3dist(pip) >= 19'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ VALAFLAGS=-g
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ CC=gcc
+ CXX=g++
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ RPM_TOXENV=py313
+ FEDORA=43
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir --output /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires -r docs/requirements.txt
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
   (installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
   (installed: Sphinx 8.2.3)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
   (installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement satisfied: setuptools>=40.8.0
   (installed: setuptools 78.1.1)
/usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: BSD License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running 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
warning: no previously-included files matching '*.py[co]' 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'
running dist_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
warning: no previously-included files matching '*.py[co]' 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'
creating '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/django-4.2.20.dist-info'
Handling asgiref<4,>=3.6.0 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: asgiref<4,>=3.6.0
   (installed: asgiref 3.8.1)
Handling backports.zoneinfo; python_version < "3.9" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: backports.zoneinfo; python_version < "3.9"
Handling sqlparse>=0.3.1 from hook generated metadata: Requires-Dist (Django)
Requirement not satisfied: sqlparse>=0.3.1
Handling tzdata; sys_platform == "win32" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: tzdata; sys_platform == "win32"
Handling argon2-cffi>=19.1.0; extra == "argon2" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: argon2-cffi>=19.1.0; extra == "argon2"
Handling bcrypt; extra == "bcrypt" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: bcrypt; extra == "bcrypt"
+ cat /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires
+ rm -rfv django-4.2.20.dist-info/
removed 'django-4.2.20.dist-info/entry_points.txt'
removed 'django-4.2.20.dist-info/top_level.txt'
removed 'django-4.2.20.dist-info/METADATA'
removed 'django-4.2.20.dist-info/licenses/LICENSE'
removed 'django-4.2.20.dist-info/licenses/LICENSE.python'
removed 'django-4.2.20.dist-info/licenses/AUTHORS'
removed directory 'django-4.2.20.dist-info/licenses'
removed directory 'django-4.2.20.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
 fedora                                 100% | 938.3 KiB/s |  27.2 KiB |  00m00s
 Copr repository                        100% |   6.5 KiB/s |   1.5 KiB |  00m00s
Repositories loaded.
Package "bash-completion-1:2.16-1.fc42.noarch" is already installed.
Package "make-1:4.4.1-10.fc42.x86_64" is already installed.
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-asgiref-3.8.1-2.fc43.noarch" is already installed.
Package "python3-devel-3.13.3-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-1.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-enchant-3.2.2-16.fc43.noarch" is already installed.
Package "python3-setuptools-78.1.1-1.fc43.noarch" is already installed.
Package "python3-sphinx-1:8.2.3-5.fc43.noarch" is already installed.
Package "python3-sphinxcontrib-spelling-7.3.3-12.fc43.noarch" is already installed.

Package           Arch   Version       Repository      Size
Installing:
 python3-sqlparse noarch 0.4.2-14.fc43 copr_base  356.6 KiB

Transaction Summary:
 Installing:         1 package

Total size of inbound packages is 107 KiB. Need to download 107 KiB.
After this operation, 357 KiB extra will be used (install 357 KiB, remove 0 B).
[1/1] python3-sqlparse-0:0.4.2-14.fc43. 100% |  25.0 KiB/s | 106.9 KiB |  00m04s
--------------------------------------------------------------------------------
[1/1] Total                             100% |  25.0 KiB/s | 106.9 KiB |  00m04s
Running transaction
[1/3] Verify package files              100% |   0.0   B/s |   1.0   B |  00m00s
[2/3] Prepare transaction               100% | 142.0   B/s |   1.0   B |  00m00s
[3/3] Installing python3-sqlparse-0:0.4 100% |  15.1 MiB/s | 371.7 KiB |  00m00s
Warning: skipped OpenPGP checks for 1 package from repository: copr_base
Complete!
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.PVAZoW
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(packaging)'
+ echo 'python3dist(pip) >= 19'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ VALAFLAGS=-g
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ CC=gcc
+ CXX=g++
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ RPM_TOXENV=py313
+ FEDORA=43
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir --output /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires -r docs/requirements.txt
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
   (installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
   (installed: Sphinx 8.2.3)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
   (installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement satisfied: setuptools>=40.8.0
   (installed: setuptools 78.1.1)
/usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: BSD License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running 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
warning: no previously-included files matching '*.py[co]' 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'
running dist_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
warning: no previously-included files matching '*.py[co]' 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'
creating '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/django-4.2.20.dist-info'
Handling asgiref<4,>=3.6.0 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: asgiref<4,>=3.6.0
   (installed: asgiref 3.8.1)
Handling backports.zoneinfo; python_version < "3.9" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: backports.zoneinfo; python_version < "3.9"
Handling sqlparse>=0.3.1 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: sqlparse>=0.3.1
   (installed: sqlparse 0.4.2)
Handling tzdata; sys_platform == "win32" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: tzdata; sys_platform == "win32"
Handling argon2-cffi>=19.1.0; extra == "argon2" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: argon2-cffi>=19.1.0; extra == "argon2"
Handling bcrypt; extra == "bcrypt" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: bcrypt; extra == "bcrypt"
+ cat /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires
+ rm -rfv django-4.2.20.dist-info/
removed 'django-4.2.20.dist-info/entry_points.txt'
removed 'django-4.2.20.dist-info/top_level.txt'
removed 'django-4.2.20.dist-info/METADATA'
removed 'django-4.2.20.dist-info/licenses/LICENSE'
removed 'django-4.2.20.dist-info/licenses/LICENSE.python'
removed 'django-4.2.20.dist-info/licenses/AUTHORS'
removed directory 'django-4.2.20.dist-info/licenses'
removed directory 'django-4.2.20.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
 fedora                                 100% |  97.9 KiB/s |  27.2 KiB |  00m00s
 Copr repository                        100% | 711.0   B/s |   1.5 KiB |  00m02s
 Copr repository                        100% | 341.9 KiB/s |   5.7 MiB |  00m17s
Repositories loaded.
Nothing to do.
Package "bash-completion-1:2.16-1.fc42.noarch" is already installed.
Package "make-1:4.4.1-10.fc42.x86_64" is already installed.
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-asgiref-3.8.1-2.fc43.noarch" is already installed.
Package "python3-devel-3.13.3-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-1.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-enchant-3.2.2-16.fc43.noarch" is already installed.
Package "python3-setuptools-78.1.1-1.fc43.noarch" is already installed.
Package "python3-sphinx-1:8.2.3-5.fc43.noarch" is already installed.
Package "python3-sphinxcontrib-spelling-7.3.3-12.fc43.noarch" is already installed.
Package "python3-sqlparse-0.4.2-14.fc43.noarch" is already installed.

Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1748908800
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.4rKYac
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(packaging)'
+ echo 'python3dist(pip) >= 19'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ VALAFLAGS=-g
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1  '
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ CC=gcc
+ CXX=g++
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ RPM_TOXENV=py313
+ FEDORA=43
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir --output /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires -r docs/requirements.txt
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
   (installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
   (installed: Sphinx 8.2.3)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
   (installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement satisfied: setuptools>=40.8.0
   (installed: setuptools 78.1.1)
/usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: BSD License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running 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
warning: no previously-included files matching '*.py[co]' 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'
running dist_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
warning: no previously-included files matching '*.py[co]' 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'
creating '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/django-4.2.20.dist-info'
Handling asgiref<4,>=3.6.0 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: asgiref<4,>=3.6.0
   (installed: asgiref 3.8.1)
Handling backports.zoneinfo; python_version < "3.9" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: backports.zoneinfo; python_version < "3.9"
Handling sqlparse>=0.3.1 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: sqlparse>=0.3.1
   (installed: sqlparse 0.4.2)
Handling tzdata; sys_platform == "win32" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: tzdata; sys_platform == "win32"
Handling argon2-cffi>=19.1.0; extra == "argon2" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: argon2-cffi>=19.1.0; extra == "argon2"
Handling bcrypt; extra == "bcrypt" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: bcrypt; extra == "bcrypt"
+ cat /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-buildrequires
+ rm -rfv django-4.2.20.dist-info/
removed 'django-4.2.20.dist-info/entry_points.txt'
removed 'django-4.2.20.dist-info/top_level.txt'
removed 'django-4.2.20.dist-info/METADATA'
removed 'django-4.2.20.dist-info/licenses/LICENSE'
removed 'django-4.2.20.dist-info/licenses/LICENSE.python'
removed 'django-4.2.20.dist-info/licenses/AUTHORS'
removed directory 'django-4.2.20.dist-info/licenses'
removed directory 'django-4.2.20.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.t3dQro
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd Django-4.2.20
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ VALAFLAGS=-g
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ CC=gcc
+ CXX=g++
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir
Processing /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20
  Preparing metadata (pyproject.toml): started
  Running command Preparing metadata (pyproject.toml)
  /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
  !!

          ********************************************************************************
          Please consider removing the following classifiers in favor of a SPDX license expression:

          License :: OSI Approved :: BSD License

          See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
          ********************************************************************************

  !!
    self._finalize_license_expression()
  running dist_info
  creating /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info
  writing /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/PKG-INFO
  writing dependency_links to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/dependency_links.txt
  writing entry points to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/entry_points.txt
  writing requirements to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/requires.txt
  writing top-level names to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/top_level.txt
  writing manifest file '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/SOURCES.txt'
  reading manifest file '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/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 '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/Django.egg-info/SOURCES.txt'
  creating '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-modern-metadata-ehzepj06/django-4.2.20.dist-info'
  Preparing metadata (pyproject.toml): finished with status 'done'
Building wheels for collected packages: Django
  Building wheel for Django (pyproject.toml): started
  Running command Building wheel for Django (pyproject.toml)
  /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
  !!

          ********************************************************************************
          Please consider removing the following classifiers in favor of a SPDX license expression:

          License :: OSI Approved :: BSD License

          See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
          ********************************************************************************

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

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.app_template.migrations' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ig.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

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


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

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

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

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

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

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

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

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

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

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.conf.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.project_template' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.project_template' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.project_template' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.project_template' to be distributed and are
          already explicitly excluding 'django.conf.project_template' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.conf.project_template.project_name' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.conf.project_template.project_name' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.conf.project_template.project_name' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.conf.project_template.project_name' to be distributed and are
          already explicitly excluding 'django.conf.project_template.project_name' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.am.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.am.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.am.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.am.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.am.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.kab.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.kab.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.kab.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.kab.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.css' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.css.vendor.select2' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.css.vendor.select2' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.css.vendor.select2' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.css.vendor.select2' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.css.vendor.select2' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.img' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.img' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.img' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.img' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.img' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.img.gis' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.img.gis' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.img.gis' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.img.gis' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.img.gis' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.js' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.js' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.js' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.js' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.admin' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.js.admin' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.js.admin' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.js.admin' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.js.admin' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.jquery' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.js.vendor.jquery' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.js.vendor.jquery' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.js.vendor.jquery' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.jquery' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.js.vendor.select2' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2.i18n' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.js.vendor.select2.i18n' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2.i18n' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.xregexp' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.static.admin.js.vendor.xregexp' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.static.admin.js.vendor.xregexp' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.static.admin.js.vendor.xregexp' to be distributed and are
          already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.xregexp' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.templates.admin' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.templates.admin' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.templates.admin' to be distributed and are
          already explicitly excluding 'django.contrib.admin.templates.admin' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.auth.user' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.templates.admin.auth.user' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.templates.admin.auth.user' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.templates.admin.auth.user' to be distributed and are
          already explicitly excluding 'django.contrib.admin.templates.admin.auth.user' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.edit_inline' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.templates.admin.edit_inline' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.templates.admin.edit_inline' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.templates.admin.edit_inline' to be distributed and are
          already explicitly excluding 'django.contrib.admin.templates.admin.edit_inline' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.includes' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.templates.admin.includes' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.templates.admin.includes' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.templates.admin.includes' to be distributed and are
          already explicitly excluding 'django.contrib.admin.templates.admin.includes' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.admin.widgets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.templates.admin.widgets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.templates.admin.widgets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.templates.admin.widgets' to be distributed and are
          already explicitly excluding 'django.contrib.admin.templates.admin.widgets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admin.templates.registration' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admin.templates.registration' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admin.templates.registration' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admin.templates.registration' to be distributed and are
          already explicitly excluding 'django.contrib.admin.templates.registration' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.kab.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.kab.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.kab.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.admindocs.templates.admin_doc' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.admindocs.templates.admin_doc' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.admindocs.templates.admin_doc' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.admindocs.templates.admin_doc' to be distributed and are
          already explicitly excluding 'django.contrib.admindocs.templates.admin_doc' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.kab.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.kab.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.kab.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.kab.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.templates.auth.widgets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.templates.auth.widgets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.templates.auth.widgets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.templates.auth.widgets' to be distributed and are
          already explicitly excluding 'django.contrib.auth.templates.auth.widgets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.auth.templates.registration' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.auth.templates.registration' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.auth.templates.registration' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.auth.templates.registration' to be distributed and are
          already explicitly excluding 'django.contrib.auth.templates.registration' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.static.gis.css' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.static.gis.css' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.static.gis.css' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.static.gis.css' to be distributed and are
          already explicitly excluding 'django.contrib.gis.static.gis.css' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.static.gis.img' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.static.gis.img' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.static.gis.img' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.static.gis.img' to be distributed and are
          already explicitly excluding 'django.contrib.gis.static.gis.img' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.static.gis.js' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.static.gis.js' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.static.gis.js' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.static.gis.js' to be distributed and are
          already explicitly excluding 'django.contrib.gis.static.gis.js' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.templates.gis' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.templates.gis' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.templates.gis' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.templates.gis' to be distributed and are
          already explicitly excluding 'django.contrib.gis.templates.gis' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.templates.gis.admin' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.templates.gis.admin' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.templates.gis.admin' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.templates.gis.admin' to be distributed and are
          already explicitly excluding 'django.contrib.gis.templates.gis.admin' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.gis.templates.gis.kml' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.gis.templates.gis.kml' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.gis.templates.gis.kml' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.gis.templates.gis.kml' to be distributed and are
          already explicitly excluding 'django.contrib.gis.templates.gis.kml' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.jinja2.postgres.widgets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.jinja2.postgres.widgets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.jinja2.postgres.widgets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.jinja2.postgres.widgets' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.jinja2.postgres.widgets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.postgres.templates.postgres.widgets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.postgres.templates.postgres.widgets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.postgres.templates.postgres.widgets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.postgres.templates.postgres.widgets' to be distributed and are
          already explicitly excluding 'django.contrib.postgres.templates.postgres.widgets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.kab.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.kab.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.kab.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.kab.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.kab.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.kab.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.kab.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.kab.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sitemaps.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sitemaps.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sitemaps.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sitemaps.templates' to be distributed and are
          already explicitly excluding 'django.contrib.sitemaps.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.af.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.af.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.af.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.af.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ar.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ar.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ar.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ar.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ast.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ast.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ast.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ast.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.az.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.az.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.az.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.az.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.be.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.be.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.be.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.be.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.bg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.bg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.bg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.bg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.bn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.bn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.bn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.bn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.br.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.br.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.br.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.br.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.bs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.bs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.bs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.bs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ca.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ca.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ca.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ca.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ckb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ckb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ckb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ckb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.cs.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.cs.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.cs.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.cs.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.cy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.cy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.cy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.cy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.da.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.da.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.da.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.da.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.de.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.de.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.de.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.de.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.dsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.dsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.dsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.dsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.el.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.el.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.el.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.el.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.en.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.en.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.en.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.en.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.en_AU.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.en_AU.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.en_AU.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.en_GB.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.en_GB.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.en_GB.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.eo.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.eo.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.eo.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.eo.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.es.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.es.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.es.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.es.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.es_AR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.es_AR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.es_AR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.es_CO.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.es_CO.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.es_CO.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.es_MX.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.es_MX.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.es_MX.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.es_VE.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.es_VE.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.es_VE.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.et.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.et.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.et.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.et.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.eu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.eu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.eu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.eu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.fa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.fa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.fa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.fa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.fi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.fi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.fi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.fi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.fr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.fr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.fr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.fr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.fy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.fy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.fy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.fy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ga.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ga.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ga.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ga.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.gd.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.gd.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.gd.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.gd.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.gl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.gl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.gl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.gl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.he.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.he.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.he.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.he.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.hi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.hi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.hi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.hi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.hr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.hr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.hr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.hr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.hsb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.hsb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.hsb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.hsb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.hu.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.hu.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.hu.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.hu.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.hy.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.hy.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.hy.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.hy.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ia.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ia.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ia.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ia.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.id.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.id.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.id.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.id.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.io.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.io.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.io.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.io.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.is.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.is.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.is.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.is.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.it.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.it.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.it.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.it.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ja.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ja.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ja.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ja.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ka.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ka.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ka.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ka.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.kab.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.kab.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.kab.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.kab.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.kk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.kk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.kk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.kk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.km.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.km.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.km.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.km.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.kn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.kn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.kn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.kn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ko.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ko.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ko.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ko.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ky.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ky.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ky.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ky.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.lb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.lb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.lb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.lb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.lt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.lt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.lt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.lt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.lv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.lv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.lv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.lv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.mk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.mk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.mk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.mk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ml.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ml.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ml.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ml.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.mn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.mn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.mn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.mn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.mr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.mr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.mr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.mr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ms.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ms.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ms.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ms.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.my.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.my.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.my.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.my.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.nb.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.nb.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.nb.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.nb.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ne.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ne.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ne.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ne.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.nl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.nl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.nl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.nl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.nn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.nn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.nn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.nn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.os.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.os.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.os.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.os.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.pa.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.pa.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.pa.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.pa.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.pl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.pl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.pl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.pl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.pt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.pt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.pt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.pt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ro.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ro.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ro.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ro.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ru.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ru.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ru.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ru.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sl.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sl.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sl.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sl.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sq.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sq.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sq.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sq.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sv.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sv.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sv.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sv.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.sw.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.sw.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.sw.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.sw.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ta.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ta.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ta.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ta.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.te.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.te.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.te.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.te.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.tg.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.tg.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.tg.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.tg.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.th.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.th.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.th.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.th.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.tk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.tk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.tk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.tk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.tr.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.tr.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.tr.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.tr.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.tt.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.tt.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.tt.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.tt.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.udm.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.udm.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.udm.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.udm.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.uk.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.uk.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.uk.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.uk.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.ur.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.ur.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.ur.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.ur.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.uz.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.uz.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.uz.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.uz.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.vi.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.vi.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.vi.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.vi.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' to be distributed and are
          already explicitly excluding 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.jinja2.django.forms' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.jinja2.django.forms' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.jinja2.django.forms' to be distributed and are
          already explicitly excluding 'django.forms.jinja2.django.forms' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.errors.dict' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.jinja2.django.forms.errors.dict' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.jinja2.django.forms.errors.dict' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.jinja2.django.forms.errors.dict' to be distributed and are
          already explicitly excluding 'django.forms.jinja2.django.forms.errors.dict' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.errors.list' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.jinja2.django.forms.errors.list' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.jinja2.django.forms.errors.list' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.jinja2.django.forms.errors.list' to be distributed and are
          already explicitly excluding 'django.forms.jinja2.django.forms.errors.list' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.formsets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.jinja2.django.forms.formsets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.jinja2.django.forms.formsets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.jinja2.django.forms.formsets' to be distributed and are
          already explicitly excluding 'django.forms.jinja2.django.forms.formsets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.jinja2.django.forms.widgets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.jinja2.django.forms.widgets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.jinja2.django.forms.widgets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.jinja2.django.forms.widgets' to be distributed and are
          already explicitly excluding 'django.forms.jinja2.django.forms.widgets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.templates.django.forms' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.templates.django.forms' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.templates.django.forms' to be distributed and are
          already explicitly excluding 'django.forms.templates.django.forms' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.errors.dict' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.templates.django.forms.errors.dict' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.templates.django.forms.errors.dict' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.templates.django.forms.errors.dict' to be distributed and are
          already explicitly excluding 'django.forms.templates.django.forms.errors.dict' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.errors.list' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.templates.django.forms.errors.list' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.templates.django.forms.errors.list' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.templates.django.forms.errors.list' to be distributed and are
          already explicitly excluding 'django.forms.templates.django.forms.errors.list' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.formsets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.templates.django.forms.formsets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.templates.django.forms.formsets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.templates.django.forms.formsets' to be distributed and are
          already explicitly excluding 'django.forms.templates.django.forms.formsets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.forms.templates.django.forms.widgets' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.forms.templates.django.forms.widgets' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.forms.templates.django.forms.widgets' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.forms.templates.django.forms.widgets' to be distributed and are
          already explicitly excluding 'django.forms.templates.django.forms.widgets' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django.views.templates' is absent from the `packages` configuration.
  !!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'django.views.templates' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.

          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'django.views.templates' is explicitly added
          to the `packages` configuration field.

          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).

          You can read more about "package discovery" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

          If you don't want 'django.views.templates' to be distributed and are
          already explicitly excluding 'django.views.templates' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.

          You can read more about "package data files" on setuptools documentation page:

          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************

  !!
    check.warn(importable)
  creating build/lib/django/conf/app_template
  copying django/conf/app_template/__init__.py-tpl -> build/lib/django/conf/app_template
  copying django/conf/app_template/admin.py-tpl -> build/lib/django/conf/app_template
  copying django/conf/app_template/apps.py-tpl -> build/lib/django/conf/app_template
  copying django/conf/app_template/models.py-tpl -> build/lib/django/conf/app_template
  copying django/conf/app_template/tests.py-tpl -> build/lib/django/conf/app_template
  copying django/conf/app_template/views.py-tpl -> build/lib/django/conf/app_template
  creating build/lib/django/conf/app_template/migrations
  copying django/conf/app_template/migrations/__init__.py-tpl -> build/lib/django/conf/app_template/migrations
  creating build/lib/django/conf/project_template
  copying django/conf/project_template/manage.py-tpl -> build/lib/django/conf/project_template
  creating build/lib/django/conf/project_template/project_name
  copying django/conf/project_template/project_name/__init__.py-tpl -> build/lib/django/conf/project_template/project_name
  copying django/conf/project_template/project_name/asgi.py-tpl -> build/lib/django/conf/project_template/project_name
  copying django/conf/project_template/project_name/settings.py-tpl -> build/lib/django/conf/project_template/project_name
  copying django/conf/project_template/project_name/urls.py-tpl -> build/lib/django/conf/project_template/project_name
  copying django/conf/project_template/project_name/wsgi.py-tpl -> build/lib/django/conf/project_template/project_name
  copying django/dispatch/license.txt -> build/lib/django/dispatch
  creating build/lib/django/forms/jinja2/django/forms
  copying django/forms/jinja2/django/forms/attrs.html -> build/lib/django/forms/jinja2/django/forms
  copying django/forms/jinja2/django/forms/default.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/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/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/default.html -> 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/django/forms
  copying django/forms/templates/django/forms/attrs.html -> build/lib/django/forms/templates/django/forms
  copying django/forms/templates/django/forms/default.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/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/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/default.html -> 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/views/templates
  copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates
  copying django/views/templates/technical_404.html -> build/lib/django/views/templates
  copying django/views/templates/technical_500.html -> build/lib/django/views/templates
  copying django/views/templates/technical_500.txt -> build/lib/django/views/templates
  creating build/lib/django/conf/locale/af/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/conf/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ur/LC_MESSAGES
  copying django/conf/locale/ur/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ur/LC_MESSAGES
  creating build/lib/django/conf/locale/ar/LC_MESSAGES
  copying django/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar/LC_MESSAGES
  copying django/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar/LC_MESSAGES
  creating build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
  copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
  copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
  creating build/lib/django/conf/locale/az/LC_MESSAGES
  copying django/conf/locale/az/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/az/LC_MESSAGES
  copying django/conf/locale/az/LC_MESSAGES/django.po -> build/lib/django/conf/locale/az/LC_MESSAGES
  creating build/lib/django/conf/locale/bg/LC_MESSAGES
  copying django/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bg/LC_MESSAGES
  copying django/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bg/LC_MESSAGES
  creating build/lib/django/conf/locale/bn/LC_MESSAGES
  copying django/conf/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bn/LC_MESSAGES
  copying django/conf/locale/bn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bn/LC_MESSAGES
  creating build/lib/django/conf/locale/bs/LC_MESSAGES
  copying django/conf/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bs/LC_MESSAGES
  copying django/conf/locale/bs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bs/LC_MESSAGES
  creating build/lib/django/conf/locale/ca/LC_MESSAGES
  copying django/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ca/LC_MESSAGES
  copying django/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ca/LC_MESSAGES
  creating build/lib/django/conf/locale/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/cs/LC_MESSAGES
  copying django/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cs/LC_MESSAGES
  copying django/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cs/LC_MESSAGES
  creating build/lib/django/conf/locale/cy/LC_MESSAGES
  copying django/conf/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cy/LC_MESSAGES
  copying django/conf/locale/cy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cy/LC_MESSAGES
  creating build/lib/django/conf/locale/da/LC_MESSAGES
  copying django/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/da/LC_MESSAGES
  copying django/conf/locale/da/LC_MESSAGES/django.po -> build/lib/django/conf/locale/da/LC_MESSAGES
  creating build/lib/django/conf/locale/de/LC_MESSAGES
  copying django/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/de/LC_MESSAGES
  copying django/conf/locale/de/LC_MESSAGES/django.po -> build/lib/django/conf/locale/de/LC_MESSAGES
  creating build/lib/django/conf/locale/el/LC_MESSAGES
  copying django/conf/locale/el/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/el/LC_MESSAGES
  copying django/conf/locale/el/LC_MESSAGES/django.po -> build/lib/django/conf/locale/el/LC_MESSAGES
  creating build/lib/django/conf/locale/en/LC_MESSAGES
  copying django/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en/LC_MESSAGES
  copying django/conf/locale/en/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en/LC_MESSAGES
  creating build/lib/django/conf/locale/en_AU/LC_MESSAGES
  copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
  copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
  creating build/lib/django/conf/locale/en_GB/LC_MESSAGES
  copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
  copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
  creating build/lib/django/conf/locale/eo/LC_MESSAGES
  copying django/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eo/LC_MESSAGES
  copying django/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eo/LC_MESSAGES
  creating build/lib/django/conf/locale/es/LC_MESSAGES
  copying django/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es/LC_MESSAGES
  copying django/conf/locale/es/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es/LC_MESSAGES
  creating build/lib/django/conf/locale/es_AR/LC_MESSAGES
  copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
  copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
  creating build/lib/django/conf/locale/es_CO/LC_MESSAGES
  copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
  copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
  creating build/lib/django/conf/locale/es_MX/LC_MESSAGES
  copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
  copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
  creating build/lib/django/conf/locale/et/LC_MESSAGES
  copying django/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/et/LC_MESSAGES
  copying django/conf/locale/et/LC_MESSAGES/django.po -> build/lib/django/conf/locale/et/LC_MESSAGES
  creating build/lib/django/conf/locale/eu/LC_MESSAGES
  copying django/conf/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eu/LC_MESSAGES
  copying django/conf/locale/eu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eu/LC_MESSAGES
  creating build/lib/django/conf/locale/fa/LC_MESSAGES
  copying django/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fa/LC_MESSAGES
  copying django/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fa/LC_MESSAGES
  creating build/lib/django/conf/locale/fi/LC_MESSAGES
  copying django/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fi/LC_MESSAGES
  copying django/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fi/LC_MESSAGES
  creating build/lib/django/conf/locale/fr/LC_MESSAGES
  copying django/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fr/LC_MESSAGES
  copying django/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fr/LC_MESSAGES
  creating build/lib/django/conf/locale/fy/LC_MESSAGES
  copying django/conf/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fy/LC_MESSAGES
  copying django/conf/locale/fy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fy/LC_MESSAGES
  creating build/lib/django/conf/locale/ga/LC_MESSAGES
  copying django/conf/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ga/LC_MESSAGES
  copying django/conf/locale/ga/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ga/LC_MESSAGES
  creating build/lib/django/conf/locale/gd/LC_MESSAGES
  copying django/conf/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gd/LC_MESSAGES
  copying django/conf/locale/gd/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gd/LC_MESSAGES
  creating build/lib/django/conf/locale/gl/LC_MESSAGES
  copying django/conf/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gl/LC_MESSAGES
  copying django/conf/locale/gl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gl/LC_MESSAGES
  creating build/lib/django/conf/locale/he/LC_MESSAGES
  copying django/conf/locale/he/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/he/LC_MESSAGES
  copying django/conf/locale/he/LC_MESSAGES/django.po -> build/lib/django/conf/locale/he/LC_MESSAGES
  creating build/lib/django/conf/locale/hi/LC_MESSAGES
  copying django/conf/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hi/LC_MESSAGES
  copying django/conf/locale/hi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hi/LC_MESSAGES
  creating build/lib/django/conf/locale/hr/LC_MESSAGES
  copying django/conf/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hr/LC_MESSAGES
  copying django/conf/locale/hr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hr/LC_MESSAGES
  creating build/lib/django/conf/locale/hu/LC_MESSAGES
  copying django/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hu/LC_MESSAGES
  copying django/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hu/LC_MESSAGES
  creating build/lib/django/conf/locale/id/LC_MESSAGES
  copying django/conf/locale/id/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/id/LC_MESSAGES
  copying django/conf/locale/id/LC_MESSAGES/django.po -> build/lib/django/conf/locale/id/LC_MESSAGES
  creating build/lib/django/conf/locale/ig/LC_MESSAGES
  copying django/conf/locale/ig/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ig/LC_MESSAGES
  copying django/conf/locale/ig/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ig/LC_MESSAGES
  creating build/lib/django/conf/locale/is/LC_MESSAGES
  copying django/conf/locale/is/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/is/LC_MESSAGES
  copying django/conf/locale/is/LC_MESSAGES/django.po -> build/lib/django/conf/locale/is/LC_MESSAGES
  creating build/lib/django/conf/locale/it/LC_MESSAGES
  copying django/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/it/LC_MESSAGES
  copying django/conf/locale/it/LC_MESSAGES/django.po -> build/lib/django/conf/locale/it/LC_MESSAGES
  creating build/lib/django/conf/locale/ja/LC_MESSAGES
  copying django/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ja/LC_MESSAGES
  copying django/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ja/LC_MESSAGES
  creating build/lib/django/conf/locale/ka/LC_MESSAGES
  copying django/conf/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ka/LC_MESSAGES
  copying django/conf/locale/ka/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ka/LC_MESSAGES
  creating build/lib/django/conf/locale/km/LC_MESSAGES
  copying django/conf/locale/km/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/km/LC_MESSAGES
  copying django/conf/locale/km/LC_MESSAGES/django.po -> build/lib/django/conf/locale/km/LC_MESSAGES
  creating build/lib/django/conf/locale/kn/LC_MESSAGES
  copying django/conf/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kn/LC_MESSAGES
  copying django/conf/locale/kn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kn/LC_MESSAGES
  creating build/lib/django/conf/locale/ko/LC_MESSAGES
  copying django/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ko/LC_MESSAGES
  copying django/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ko/LC_MESSAGES
  creating build/lib/django/conf/locale/ky/LC_MESSAGES
  copying django/conf/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ky/LC_MESSAGES
  copying django/conf/locale/ky/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ky/LC_MESSAGES
  creating build/lib/django/conf/locale/lt/LC_MESSAGES
  copying django/conf/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lt/LC_MESSAGES
  copying django/conf/locale/lt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lt/LC_MESSAGES
  creating build/lib/django/conf/locale/lv/LC_MESSAGES
  copying django/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lv/LC_MESSAGES
  copying django/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lv/LC_MESSAGES
  creating build/lib/django/conf/locale/mk/LC_MESSAGES
  copying django/conf/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mk/LC_MESSAGES
  copying django/conf/locale/mk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mk/LC_MESSAGES
  creating build/lib/django/conf/locale/ml/LC_MESSAGES
  copying django/conf/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ml/LC_MESSAGES
  copying django/conf/locale/ml/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ml/LC_MESSAGES
  creating build/lib/django/conf/locale/mn/LC_MESSAGES
  copying django/conf/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mn/LC_MESSAGES
  copying django/conf/locale/mn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mn/LC_MESSAGES
  creating build/lib/django/conf/locale/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/nb/LC_MESSAGES
  copying django/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nb/LC_MESSAGES
  copying django/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nb/LC_MESSAGES
  creating build/lib/django/conf/locale/nl/LC_MESSAGES
  copying django/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nl/LC_MESSAGES
  copying django/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nl/LC_MESSAGES
  creating build/lib/django/conf/locale/nn/LC_MESSAGES
  copying django/conf/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nn/LC_MESSAGES
  copying django/conf/locale/nn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nn/LC_MESSAGES
  creating build/lib/django/conf/locale/pl/LC_MESSAGES
  copying django/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pl/LC_MESSAGES
  copying django/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pl/LC_MESSAGES
  creating build/lib/django/conf/locale/pt/LC_MESSAGES
  copying django/conf/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt/LC_MESSAGES
  copying django/conf/locale/pt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt/LC_MESSAGES
  creating build/lib/django/conf/locale/pt_BR/LC_MESSAGES
  copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
  copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
  creating build/lib/django/conf/locale/ro/LC_MESSAGES
  copying django/conf/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ro/LC_MESSAGES
  copying django/conf/locale/ro/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ro/LC_MESSAGES
  creating build/lib/django/conf/locale/ru/LC_MESSAGES
  copying django/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ru/LC_MESSAGES
  copying django/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ru/LC_MESSAGES
  creating build/lib/django/conf/locale/sk/LC_MESSAGES
  copying django/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sk/LC_MESSAGES
  copying django/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sk/LC_MESSAGES
  creating build/lib/django/conf/locale/sl/LC_MESSAGES
  copying django/conf/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sl/LC_MESSAGES
  copying django/conf/locale/sl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sl/LC_MESSAGES
  creating build/lib/django/conf/locale/sq/LC_MESSAGES
  copying django/conf/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sq/LC_MESSAGES
  copying django/conf/locale/sq/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sq/LC_MESSAGES
  creating build/lib/django/conf/locale/sr/LC_MESSAGES
  copying django/conf/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr/LC_MESSAGES
  copying django/conf/locale/sr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr/LC_MESSAGES
  creating build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
  copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
  copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
  creating build/lib/django/conf/locale/sv/LC_MESSAGES
  copying django/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sv/LC_MESSAGES
  copying django/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sv/LC_MESSAGES
  creating build/lib/django/conf/locale/ta/LC_MESSAGES
  copying django/conf/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ta/LC_MESSAGES
  copying django/conf/locale/ta/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ta/LC_MESSAGES
  creating build/lib/django/conf/locale/te/LC_MESSAGES
  copying django/conf/locale/te/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/te/LC_MESSAGES
  copying django/conf/locale/te/LC_MESSAGES/django.po -> build/lib/django/conf/locale/te/LC_MESSAGES
  creating build/lib/django/conf/locale/tg/LC_MESSAGES
  copying django/conf/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tg/LC_MESSAGES
  copying django/conf/locale/tg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tg/LC_MESSAGES
  creating build/lib/django/conf/locale/th/LC_MESSAGES
  copying django/conf/locale/th/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/th/LC_MESSAGES
  copying django/conf/locale/th/LC_MESSAGES/django.po -> build/lib/django/conf/locale/th/LC_MESSAGES
  creating build/lib/django/conf/locale/tk/LC_MESSAGES
  copying django/conf/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tk/LC_MESSAGES
  copying django/conf/locale/tk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tk/LC_MESSAGES
  creating build/lib/django/conf/locale/tr/LC_MESSAGES
  copying django/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tr/LC_MESSAGES
  copying django/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tr/LC_MESSAGES
  creating build/lib/django/conf/locale/uk/LC_MESSAGES
  copying django/conf/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uk/LC_MESSAGES
  copying django/conf/locale/uk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uk/LC_MESSAGES
  creating build/lib/django/conf/locale/uz/LC_MESSAGES
  copying django/conf/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uz/LC_MESSAGES
  copying django/conf/locale/uz/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uz/LC_MESSAGES
  creating build/lib/django/conf/locale/vi/LC_MESSAGES
  copying django/conf/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/vi/LC_MESSAGES
  copying django/conf/locale/vi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/vi/LC_MESSAGES
  creating build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
  copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
  copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
  creating build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
  copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
  copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
  creating build/lib/django/contrib/admin/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
  copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
  copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
  copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/admin/locale/uk/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/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/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/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/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/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/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/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-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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
  copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/admindocs/locale/uk/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
  copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/auth/locale/uk/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/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/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/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/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/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/auth/widgets
  copying django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/lib/django/contrib/auth/templates/auth/widgets
  creating build/lib/django/contrib/auth/templates/registration
  copying django/contrib/auth/templates/registration/password_reset_subject.txt -> build/lib/django/contrib/auth/templates/registration
  creating build/lib/django/contrib/contenttypes/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
  copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/contenttypes/locale/uk/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
  copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/flatpages/locale/uk/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/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/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/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/LC_MESSAGES
  copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
  copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
  creating build/lib/django/contrib/gis/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
  copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/gis/locale/uk/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/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/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/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/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/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/gis
  copying django/contrib/gis/templates/gis/openlayers-osm.html -> build/lib/django/contrib/gis/templates/gis
  copying django/contrib/gis/templates/gis/openlayers.html -> build/lib/django/contrib/gis/templates/gis
  creating build/lib/django/contrib/gis/templates/gis/admin
  copying django/contrib/gis/templates/gis/admin/openlayers.html -> build/lib/django/contrib/gis/templates/gis/admin
  copying django/contrib/gis/templates/gis/admin/openlayers.js -> build/lib/django/contrib/gis/templates/gis/admin
  copying django/contrib/gis/templates/gis/admin/osm.html -> build/lib/django/contrib/gis/templates/gis/admin
  copying django/contrib/gis/templates/gis/admin/osm.js -> build/lib/django/contrib/gis/templates/gis/admin
  creating build/lib/django/contrib/gis/templates/gis/kml
  copying django/contrib/gis/templates/gis/kml/base.kml -> build/lib/django/contrib/gis/templates/gis/kml
  copying django/contrib/gis/templates/gis/kml/placemarks.kml -> build/lib/django/contrib/gis/templates/gis/kml
  creating build/lib/django/contrib/humanize/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
  copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/humanize/locale/uk/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
  copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
  creating build/lib/django/contrib/postgres/jinja2/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
  copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
  creating build/lib/django/contrib/postgres/locale/uk/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/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/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/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/postgres/widgets
  copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/templates/postgres/widgets
  creating build/lib/django/contrib/redirects/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
  copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/redirects/locale/uk/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
  copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
  creating build/lib/django/contrib/sessions/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
  copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/sessions/locale/uk/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
  copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
  creating build/lib/django/contrib/sitemaps/templates
  copying django/contrib/sitemaps/templates/sitemap.xml -> build/lib/django/contrib/sitemaps/templates
  copying django/contrib/sitemaps/templates/sitemap_index.xml -> build/lib/django/contrib/sitemaps/templates
  creating build/lib/django/contrib/sites/locale/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
  copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
  creating build/lib/django/contrib/sites/locale/uk/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/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/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/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/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/LC_MESSAGES
  copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
  copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
  copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal
  copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos
  installing to build/bdist.linux-x86_64/wheel
  running install
  running install_lib
  creating build/bdist.linux-x86_64/wheel
  creating build/bdist.linux-x86_64/wheel/django
  copying build/lib/django/__init__.py -> build/bdist.linux-x86_64/wheel/./django
  copying build/lib/django/__main__.py -> build/bdist.linux-x86_64/wheel/./django
  copying build/lib/django/shortcuts.py -> build/bdist.linux-x86_64/wheel/./django
  creating build/bdist.linux-x86_64/wheel/django/apps
  copying build/lib/django/apps/__init__.py -> build/bdist.linux-x86_64/wheel/./django/apps
  copying build/lib/django/apps/config.py -> build/bdist.linux-x86_64/wheel/./django/apps
  copying build/lib/django/apps/registry.py -> build/bdist.linux-x86_64/wheel/./django/apps
  creating build/bdist.linux-x86_64/wheel/django/conf
  copying build/lib/django/conf/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf
  copying build/lib/django/conf/global_settings.py -> build/bdist.linux-x86_64/wheel/./django/conf
  creating build/bdist.linux-x86_64/wheel/django/conf/locale
  copying build/lib/django/conf/locale/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar
  copying build/lib/django/conf/locale/ar/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar
  copying build/lib/django/conf/locale/ar/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES
  copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar/LC_MESSAGES
  copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ
  copying build/lib/django/conf/locale/ar_DZ/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar_DZ
  copying build/lib/django/conf/locale/ar_DZ/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/az
  copying build/lib/django/conf/locale/az/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/az
  copying build/lib/django/conf/locale/az/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/az
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES
  copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/az/LC_MESSAGES
  copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/bg
  copying build/lib/django/conf/locale/bg/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bg
  copying build/lib/django/conf/locale/bg/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES
  copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bg/LC_MESSAGES
  copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/bn
  copying build/lib/django/conf/locale/bn/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bn
  copying build/lib/django/conf/locale/bn/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES
  copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bn/LC_MESSAGES
  copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/bs
  copying build/lib/django/conf/locale/bs/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bs
  copying build/lib/django/conf/locale/bs/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES
  copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bs/LC_MESSAGES
  copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ca
  copying build/lib/django/conf/locale/ca/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ca
  copying build/lib/django/conf/locale/ca/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES
  copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ca/LC_MESSAGES
  copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ckb
  copying build/lib/django/conf/locale/ckb/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ckb
  copying build/lib/django/conf/locale/ckb/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES
  copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ckb/LC_MESSAGES
  copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/cs
  copying build/lib/django/conf/locale/cs/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cs
  copying build/lib/django/conf/locale/cs/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES
  copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cs/LC_MESSAGES
  copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/cy
  copying build/lib/django/conf/locale/cy/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cy
  copying build/lib/django/conf/locale/cy/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES
  copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cy/LC_MESSAGES
  copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/da
  copying build/lib/django/conf/locale/da/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/da
  copying build/lib/django/conf/locale/da/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/da
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES
  copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/da/LC_MESSAGES
  copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/de
  copying build/lib/django/conf/locale/de/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/de
  copying build/lib/django/conf/locale/de/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/de
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES
  copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/de/LC_MESSAGES
  copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH
  copying build/lib/django/conf/locale/de_CH/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/de_CH
  copying build/lib/django/conf/locale/de_CH/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/de_CH
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/el
  copying build/lib/django/conf/locale/el/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/el
  copying build/lib/django/conf/locale/el/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/el
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES
  copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/el/LC_MESSAGES
  copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/en
  copying build/lib/django/conf/locale/en/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en
  copying build/lib/django/conf/locale/en/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES
  copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en/LC_MESSAGES
  copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU
  copying build/lib/django/conf/locale/en_AU/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_AU
  copying build/lib/django/conf/locale/en_AU/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES
  copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_AU/LC_MESSAGES
  copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB
  copying build/lib/django/conf/locale/en_GB/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_GB
  copying build/lib/django/conf/locale/en_GB/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES
  copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_GB/LC_MESSAGES
  copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/eo
  copying build/lib/django/conf/locale/eo/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eo
  copying build/lib/django/conf/locale/eo/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES
  copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eo/LC_MESSAGES
  copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es
  copying build/lib/django/conf/locale/es/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es
  copying build/lib/django/conf/locale/es/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES
  copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es/LC_MESSAGES
  copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR
  copying build/lib/django/conf/locale/es_AR/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_AR
  copying build/lib/django/conf/locale/es_AR/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES
  copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_AR/LC_MESSAGES
  copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO
  copying build/lib/django/conf/locale/es_CO/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_CO
  copying build/lib/django/conf/locale/es_CO/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES
  copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_CO/LC_MESSAGES
  copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX
  copying build/lib/django/conf/locale/es_MX/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_MX
  copying build/lib/django/conf/locale/es_MX/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES
  copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_MX/LC_MESSAGES
  copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI
  copying build/lib/django/conf/locale/es_NI/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_NI
  copying build/lib/django/conf/locale/es_NI/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_NI
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR
  copying build/lib/django/conf/locale/es_PR/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_PR
  copying build/lib/django/conf/locale/es_PR/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_PR
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/et
  copying build/lib/django/conf/locale/et/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/et
  copying build/lib/django/conf/locale/et/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/et
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES
  copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/et/LC_MESSAGES
  copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/eu
  copying build/lib/django/conf/locale/eu/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eu
  copying build/lib/django/conf/locale/eu/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES
  copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eu/LC_MESSAGES
  copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fa
  copying build/lib/django/conf/locale/fa/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fa
  copying build/lib/django/conf/locale/fa/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES
  copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fa/LC_MESSAGES
  copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fi
  copying build/lib/django/conf/locale/fi/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fi
  copying build/lib/django/conf/locale/fi/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES
  copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fi/LC_MESSAGES
  copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fr
  copying build/lib/django/conf/locale/fr/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fr
  copying build/lib/django/conf/locale/fr/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES
  copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fr/LC_MESSAGES
  copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fy
  copying build/lib/django/conf/locale/fy/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fy
  copying build/lib/django/conf/locale/fy/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES
  copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fy/LC_MESSAGES
  copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ga
  copying build/lib/django/conf/locale/ga/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ga
  copying build/lib/django/conf/locale/ga/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES
  copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ga/LC_MESSAGES
  copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/gd
  copying build/lib/django/conf/locale/gd/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gd
  copying build/lib/django/conf/locale/gd/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES
  copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gd/LC_MESSAGES
  copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/gl
  copying build/lib/django/conf/locale/gl/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gl
  copying build/lib/django/conf/locale/gl/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES
  copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gl/LC_MESSAGES
  copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/he
  copying build/lib/django/conf/locale/he/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/he
  copying build/lib/django/conf/locale/he/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/he
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES
  copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/he/LC_MESSAGES
  copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hi
  copying build/lib/django/conf/locale/hi/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hi
  copying build/lib/django/conf/locale/hi/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES
  copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hi/LC_MESSAGES
  copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hr
  copying build/lib/django/conf/locale/hr/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hr
  copying build/lib/django/conf/locale/hr/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES
  copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hr/LC_MESSAGES
  copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hu
  copying build/lib/django/conf/locale/hu/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hu
  copying build/lib/django/conf/locale/hu/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES
  copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hu/LC_MESSAGES
  copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/id
  copying build/lib/django/conf/locale/id/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/id
  copying build/lib/django/conf/locale/id/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/id
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES
  copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/id/LC_MESSAGES
  copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ig
  copying build/lib/django/conf/locale/ig/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ig
  copying build/lib/django/conf/locale/ig/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ig
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES
  copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ig/LC_MESSAGES
  copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ig/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/is
  copying build/lib/django/conf/locale/is/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/is
  copying build/lib/django/conf/locale/is/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/is
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES
  copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/is/LC_MESSAGES
  copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/it
  copying build/lib/django/conf/locale/it/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/it
  copying build/lib/django/conf/locale/it/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/it
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES
  copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/it/LC_MESSAGES
  copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ja
  copying build/lib/django/conf/locale/ja/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ja
  copying build/lib/django/conf/locale/ja/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES
  copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ja/LC_MESSAGES
  copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ka
  copying build/lib/django/conf/locale/ka/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ka
  copying build/lib/django/conf/locale/ka/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES
  copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ka/LC_MESSAGES
  copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/km
  copying build/lib/django/conf/locale/km/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/km
  copying build/lib/django/conf/locale/km/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/km
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES
  copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/km/LC_MESSAGES
  copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/kn
  copying build/lib/django/conf/locale/kn/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kn
  copying build/lib/django/conf/locale/kn/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES
  copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kn/LC_MESSAGES
  copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ko
  copying build/lib/django/conf/locale/ko/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ko
  copying build/lib/django/conf/locale/ko/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES
  copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ko/LC_MESSAGES
  copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ky
  copying build/lib/django/conf/locale/ky/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ky
  copying build/lib/django/conf/locale/ky/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES
  copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ky/LC_MESSAGES
  copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/lt
  copying build/lib/django/conf/locale/lt/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lt
  copying build/lib/django/conf/locale/lt/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES
  copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lt/LC_MESSAGES
  copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/lv
  copying build/lib/django/conf/locale/lv/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lv
  copying build/lib/django/conf/locale/lv/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES
  copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lv/LC_MESSAGES
  copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/mk
  copying build/lib/django/conf/locale/mk/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mk
  copying build/lib/django/conf/locale/mk/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES
  copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mk/LC_MESSAGES
  copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ml
  copying build/lib/django/conf/locale/ml/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ml
  copying build/lib/django/conf/locale/ml/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES
  copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ml/LC_MESSAGES
  copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/mn
  copying build/lib/django/conf/locale/mn/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mn
  copying build/lib/django/conf/locale/mn/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES
  copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mn/LC_MESSAGES
  copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ms
  copying build/lib/django/conf/locale/ms/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ms
  copying build/lib/django/conf/locale/ms/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES
  copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ms/LC_MESSAGES
  copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/nb
  copying build/lib/django/conf/locale/nb/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nb
  copying build/lib/django/conf/locale/nb/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES
  copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nb/LC_MESSAGES
  copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/nl
  copying build/lib/django/conf/locale/nl/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nl
  copying build/lib/django/conf/locale/nl/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES
  copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nl/LC_MESSAGES
  copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/nn
  copying build/lib/django/conf/locale/nn/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nn
  copying build/lib/django/conf/locale/nn/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES
  copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nn/LC_MESSAGES
  copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pl
  copying build/lib/django/conf/locale/pl/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pl
  copying build/lib/django/conf/locale/pl/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES
  copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pl/LC_MESSAGES
  copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt
  copying build/lib/django/conf/locale/pt/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt
  copying build/lib/django/conf/locale/pt/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES
  copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt/LC_MESSAGES
  copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR
  copying build/lib/django/conf/locale/pt_BR/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt_BR
  copying build/lib/django/conf/locale/pt_BR/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ro
  copying build/lib/django/conf/locale/ro/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ro
  copying build/lib/django/conf/locale/ro/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES
  copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ro/LC_MESSAGES
  copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ru
  copying build/lib/django/conf/locale/ru/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ru
  copying build/lib/django/conf/locale/ru/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES
  copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ru/LC_MESSAGES
  copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sk
  copying build/lib/django/conf/locale/sk/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sk
  copying build/lib/django/conf/locale/sk/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES
  copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sk/LC_MESSAGES
  copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sl
  copying build/lib/django/conf/locale/sl/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sl
  copying build/lib/django/conf/locale/sl/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES
  copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sl/LC_MESSAGES
  copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sq
  copying build/lib/django/conf/locale/sq/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sq
  copying build/lib/django/conf/locale/sq/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES
  copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sq/LC_MESSAGES
  copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr
  copying build/lib/django/conf/locale/sr/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr
  copying build/lib/django/conf/locale/sr/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES
  copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr/LC_MESSAGES
  copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn
  copying build/lib/django/conf/locale/sr_Latn/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr_Latn
  copying build/lib/django/conf/locale/sr_Latn/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sv
  copying build/lib/django/conf/locale/sv/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sv
  copying build/lib/django/conf/locale/sv/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES
  copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sv/LC_MESSAGES
  copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ta
  copying build/lib/django/conf/locale/ta/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ta
  copying build/lib/django/conf/locale/ta/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES
  copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ta/LC_MESSAGES
  copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/te
  copying build/lib/django/conf/locale/te/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/te
  copying build/lib/django/conf/locale/te/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/te
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES
  copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/te/LC_MESSAGES
  copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tg
  copying build/lib/django/conf/locale/tg/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tg
  copying build/lib/django/conf/locale/tg/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES
  copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tg/LC_MESSAGES
  copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/th
  copying build/lib/django/conf/locale/th/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/th
  copying build/lib/django/conf/locale/th/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/th
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES
  copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/th/LC_MESSAGES
  copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tk
  copying build/lib/django/conf/locale/tk/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tk
  copying build/lib/django/conf/locale/tk/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES
  copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tk/LC_MESSAGES
  copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tr
  copying build/lib/django/conf/locale/tr/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tr
  copying build/lib/django/conf/locale/tr/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES
  copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tr/LC_MESSAGES
  copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/uk
  copying build/lib/django/conf/locale/uk/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uk
  copying build/lib/django/conf/locale/uk/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES
  copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uk/LC_MESSAGES
  copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/uz
  copying build/lib/django/conf/locale/uz/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uz
  copying build/lib/django/conf/locale/uz/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES
  copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uz/LC_MESSAGES
  copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/vi
  copying build/lib/django/conf/locale/vi/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/vi
  copying build/lib/django/conf/locale/vi/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES
  copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/vi/LC_MESSAGES
  copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans
  copying build/lib/django/conf/locale/zh_Hans/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hans
  copying build/lib/django/conf/locale/zh_Hans/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant
  copying build/lib/django/conf/locale/zh_Hant/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hant
  copying build/lib/django/conf/locale/zh_Hant/formats.py -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/af
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES
  copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/af/LC_MESSAGES
  copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES
  copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ast/LC_MESSAGES
  copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/be
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES
  copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/be/LC_MESSAGES
  copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/br
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES
  copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/br/LC_MESSAGES
  copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES
  copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/dsb/LC_MESSAGES
  copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES
  copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_VE/LC_MESSAGES
  copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES
  copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hsb/LC_MESSAGES
  copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES
  copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hy/LC_MESSAGES
  copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES
  copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ia/LC_MESSAGES
  copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/io
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES
  copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/io/LC_MESSAGES
  copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES
  copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kab/LC_MESSAGES
  copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES
  copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kk/LC_MESSAGES
  copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES
  copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lb/LC_MESSAGES
  copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES
  copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mr/LC_MESSAGES
  copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/my
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES
  copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/my/LC_MESSAGES
  copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES
  copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ne/LC_MESSAGES
  copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/os
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES
  copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/os/LC_MESSAGES
  copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES
  copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pa/LC_MESSAGES
  copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES
  copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sw/LC_MESSAGES
  copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES
  copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tt/LC_MESSAGES
  copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES
  copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/udm/LC_MESSAGES
  copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES
  copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ur/LC_MESSAGES
  copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/conf/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/conf/urls
  copying build/lib/django/conf/urls/__init__.py -> build/bdist.linux-x86_64/wheel/./django/conf/urls
  copying build/lib/django/conf/urls/i18n.py -> build/bdist.linux-x86_64/wheel/./django/conf/urls
  copying build/lib/django/conf/urls/static.py -> build/bdist.linux-x86_64/wheel/./django/conf/urls
  creating build/bdist.linux-x86_64/wheel/django/conf/app_template
  copying build/lib/django/conf/app_template/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template
  copying build/lib/django/conf/app_template/admin.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template
  copying build/lib/django/conf/app_template/apps.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template
  copying build/lib/django/conf/app_template/models.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template
  copying build/lib/django/conf/app_template/tests.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template
  copying build/lib/django/conf/app_template/views.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template
  creating build/bdist.linux-x86_64/wheel/django/conf/app_template/migrations
  copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/app_template/migrations
  creating build/bdist.linux-x86_64/wheel/django/conf/project_template
  copying build/lib/django/conf/project_template/manage.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/project_template
  creating build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
  copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/project_template/project_name
  copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/project_template/project_name
  copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/project_template/project_name
  copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/project_template/project_name
  copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> build/bdist.linux-x86_64/wheel/./django/conf/project_template/project_name
  creating build/bdist.linux-x86_64/wheel/django/contrib
  copying build/lib/django/contrib/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin
  copying build/lib/django/contrib/admin/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/actions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/checks.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/decorators.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/exceptions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/filters.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/forms.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/helpers.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/options.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/sites.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/tests.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  copying build/lib/django/contrib/admin/widgets.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations
  copying build/lib/django/contrib/admin/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/migrations
  copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/migrations
  copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/migrations
  copying build/lib/django/contrib/admin/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/migrations
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
  copying build/lib/django/contrib/admin/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templatetags
  copying build/lib/django/contrib/admin/templatetags/admin_list.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templatetags
  copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templatetags
  copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templatetags
  copying build/lib/django/contrib/admin/templatetags/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templatetags
  copying build/lib/django/contrib/admin/templatetags/log.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templatetags
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/views
  copying build/lib/django/contrib/admin/views/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/views
  copying build/lib/django/contrib/admin/views/autocomplete.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/views
  copying build/lib/django/contrib/admin/views/decorators.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/views
  copying build/lib/django/contrib/admin/views/main.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/views
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/am/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/am/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/base.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/dark_mode.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/forms.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/login.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2
  copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css/vendor/select2
  copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css/vendor/select2
  copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/css/vendor/select2
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/README.txt -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/search.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis
  copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img/gis
  copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/img/gis
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/actions.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/core.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/filters.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/theme.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin
  copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/admin
  copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/admin
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
  copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
  copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
  copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/jquery
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/select2/i18n
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
  copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
  copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
  copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/static/admin/js/vendor/xregexp
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/404.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/500.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/actions.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/app_index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/app_list.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/base.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/base_site.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/change_form.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/change_list.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/color_theme_toggle.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/filter.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/login.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/object_history.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/pagination.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/search_form.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user
  copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/auth/user
  copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/auth/user
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline
  copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/edit_inline
  copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/edit_inline
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes
  copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/includes
  copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/includes
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/date.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/time.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/admin/widgets
  creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admin/templates/registration
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs
  copying build/lib/django/contrib/admindocs/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs
  copying build/lib/django/contrib/admindocs/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs
  copying build/lib/django/contrib/admindocs/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs
  copying build/lib/django/contrib/admindocs/urls.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs
  copying build/lib/django/contrib/admindocs/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs
  copying build/lib/django/contrib/admindocs/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates
  creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> build/bdist.linux-x86_64/wheel/./django/contrib/admindocs/templates/admin_doc
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth
  copying build/lib/django/contrib/auth/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/admin.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/backends.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/base_user.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/checks.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/context_processors.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/decorators.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/forms.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/hashers.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/mixins.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/password_validation.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/signals.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/tokens.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/urls.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/validators.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  copying build/lib/django/contrib/auth/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers
  copying build/lib/django/contrib/auth/handlers/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/handlers
  copying build/lib/django/contrib/auth/handlers/modwsgi.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/handlers
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/management
  copying build/lib/django/contrib/auth/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/management
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands
  copying build/lib/django/contrib/auth/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/management/commands
  copying build/lib/django/contrib/auth/management/commands/changepassword.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/management/commands
  copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/management/commands
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/migrations
  copying build/lib/django/contrib/auth/common-passwords.txt.gz -> build/bdist.linux-x86_64/wheel/./django/contrib/auth
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth/widgets
  copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/templates/auth/widgets
  creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/registration
  copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> build/bdist.linux-x86_64/wheel/./django/contrib/auth/templates/registration
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/admin.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/checks.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/fields.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/forms.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  copying build/lib/django/contrib/contenttypes/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management
  copying build/lib/django/contrib/contenttypes/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/management
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands
  copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/management/commands
  copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/management/commands
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations
  copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/migrations
  copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/migrations
  copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/migrations
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/admin.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/forms.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/sitemaps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/urls.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  copying build/lib/django/contrib/flatpages/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations
  copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/migrations
  copying build/lib/django/contrib/flatpages/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/migrations
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags
  copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/templatetags
  copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/templatetags
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis
  copying build/lib/django/contrib/gis/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/feeds.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/geometry.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/measure.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/ptr.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/shortcuts.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  copying build/lib/django/contrib/gis/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/admin
  copying build/lib/django/contrib/gis/admin/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/admin
  copying build/lib/django/contrib/gis/admin/options.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/admin
  copying build/lib/django/contrib/gis/admin/widgets.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/admin
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db
  copying build/lib/django/contrib/gis/db/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends
  copying build/lib/django/contrib/gis/db/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends
  copying build/lib/django/contrib/gis/db/backends/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
  copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/base
  copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/base
  copying build/lib/django/contrib/gis/db/backends/base/features.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/base
  copying build/lib/django/contrib/gis/db/backends/base/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/base
  copying build/lib/django/contrib/gis/db/backends/base/operations.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/base
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
  copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/mysql
  copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/mysql
  copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/mysql
  copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/mysql
  copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/mysql
  copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/mysql
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/oracle
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/postgis
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/backends/spatialite
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
  copying build/lib/django/contrib/gis/db/models/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models
  copying build/lib/django/contrib/gis/db/models/aggregates.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models
  copying build/lib/django/contrib/gis/db/models/fields.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models
  copying build/lib/django/contrib/gis/db/models/functions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models
  copying build/lib/django/contrib/gis/db/models/lookups.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models
  copying build/lib/django/contrib/gis/db/models/proxy.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql
  copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models/sql
  copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/db/models/sql
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/forms
  copying build/lib/django/contrib/gis/forms/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/forms
  copying build/lib/django/contrib/gis/forms/fields.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/forms
  copying build/lib/django/contrib/gis/forms/widgets.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/forms
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/datasource.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/driver.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/envelope.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/error.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/feature.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/field.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/geometries.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/geomtype.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/layer.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/libgdal.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  copying build/lib/django/contrib/gis/gdal/srs.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/prototypes
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
  copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/raster
  copying build/lib/django/contrib/gis/gdal/raster/band.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/raster
  copying build/lib/django/contrib/gis/gdal/raster/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/raster
  copying build/lib/django/contrib/gis/gdal/raster/const.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/raster
  copying build/lib/django/contrib/gis/gdal/raster/source.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal/raster
  copying build/lib/django/contrib/gis/gdal/LICENSE -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/gdal
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2
  copying build/lib/django/contrib/gis/geoip2/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geoip2
  copying build/lib/django/contrib/gis/geoip2/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geoip2
  copying build/lib/django/contrib/gis/geoip2/resources.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geoip2
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/collections.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/coordseq.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/error.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/factory.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/geometry.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/io.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/libgeos.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/linestring.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/mutable_list.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/point.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/polygon.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  copying build/lib/django/contrib/gis/geos/prepared.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/io.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos/prototypes
  copying build/lib/django/contrib/gis/geos/LICENSE -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/geos
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/management
  copying build/lib/django/contrib/gis/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/management
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands
  copying build/lib/django/contrib/gis/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/management/commands
  copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/management/commands
  copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/management/commands
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers
  copying build/lib/django/contrib/gis/serializers/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/serializers
  copying build/lib/django/contrib/gis/serializers/geojson.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/serializers
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps
  copying build/lib/django/contrib/gis/sitemaps/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/sitemaps
  copying build/lib/django/contrib/gis/sitemaps/kml.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/sitemaps
  copying build/lib/django/contrib/gis/sitemaps/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/sitemaps
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
  copying build/lib/django/contrib/gis/utils/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/utils
  copying build/lib/django/contrib/gis/utils/layermapping.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/utils
  copying build/lib/django/contrib/gis/utils/ogrinfo.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/utils
  copying build/lib/django/contrib/gis/utils/ogrinspect.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/utils
  copying build/lib/django/contrib/gis/utils/srs.py -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/utils
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/css
  copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/css
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
  copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/img
  copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/img
  copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/img
  copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/img
  copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/img
  copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/img
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/js
  copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/static/gis/js
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis
  copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis
  copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin
  copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.html -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis/admin
  copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.js -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis/admin
  copying build/lib/django/contrib/gis/templates/gis/admin/osm.html -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis/admin
  copying build/lib/django/contrib/gis/templates/gis/admin/osm.js -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis/admin
  creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml
  copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis/kml
  copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> build/bdist.linux-x86_64/wheel/./django/contrib/gis/templates/gis/kml
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize
  copying build/lib/django/contrib/humanize/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize
  copying build/lib/django/contrib/humanize/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags
  copying build/lib/django/contrib/humanize/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/templatetags
  copying build/lib/django/contrib/humanize/templatetags/humanize.py -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/templatetags
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/messages
  copying build/lib/django/contrib/messages/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/api.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/constants.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/context_processors.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  copying build/lib/django/contrib/messages/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages
  creating build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
  copying build/lib/django/contrib/messages/storage/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages/storage
  copying build/lib/django/contrib/messages/storage/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages/storage
  copying build/lib/django/contrib/messages/storage/cookie.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages/storage
  copying build/lib/django/contrib/messages/storage/fallback.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages/storage
  copying build/lib/django/contrib/messages/storage/session.py -> build/bdist.linux-x86_64/wheel/./django/contrib/messages/storage
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres
  copying build/lib/django/contrib/postgres/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/constraints.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/expressions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/functions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/indexes.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/lookups.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/operations.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/search.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/serializers.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/signals.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  copying build/lib/django/contrib/postgres/validators.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates
  copying build/lib/django/contrib/postgres/aggregates/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/aggregates
  copying build/lib/django/contrib/postgres/aggregates/general.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/aggregates
  copying build/lib/django/contrib/postgres/aggregates/mixins.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/aggregates
  copying build/lib/django/contrib/postgres/aggregates/statistics.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/aggregates
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/array.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/citext.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/hstore.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/jsonb.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/ranges.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  copying build/lib/django/contrib/postgres/fields/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/fields
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms
  copying build/lib/django/contrib/postgres/forms/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/forms
  copying build/lib/django/contrib/postgres/forms/array.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/forms
  copying build/lib/django/contrib/postgres/forms/hstore.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/forms
  copying build/lib/django/contrib/postgres/forms/ranges.py -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/forms
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres/widgets
  copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/jinja2/postgres/widgets
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres
  creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres/widgets
  copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/bdist.linux-x86_64/wheel/./django/contrib/postgres/templates/postgres/widgets
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects
  copying build/lib/django/contrib/redirects/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects
  copying build/lib/django/contrib/redirects/admin.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects
  copying build/lib/django/contrib/redirects/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects
  copying build/lib/django/contrib/redirects/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects
  copying build/lib/django/contrib/redirects/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations
  copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/migrations
  copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/migrations
  copying build/lib/django/contrib/redirects/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/migrations
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions
  copying build/lib/django/contrib/sessions/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  copying build/lib/django/contrib/sessions/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  copying build/lib/django/contrib/sessions/base_session.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  copying build/lib/django/contrib/sessions/exceptions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  copying build/lib/django/contrib/sessions/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  copying build/lib/django/contrib/sessions/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  copying build/lib/django/contrib/sessions/serializers.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/base.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/cache.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/cached_db.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/db.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/file.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/backends
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/management
  copying build/lib/django/contrib/sessions/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/management
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands
  copying build/lib/django/contrib/sessions/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/management/commands
  copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/management/commands
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations
  copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/migrations
  copying build/lib/django/contrib/sessions/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/migrations
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps
  copying build/lib/django/contrib/sitemaps/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps
  copying build/lib/django/contrib/sitemaps/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps
  copying build/lib/django/contrib/sitemaps/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps
  creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management
  copying build/lib/django/contrib/sitemaps/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps/management
  creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands
  copying build/lib/django/contrib/sitemaps/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps/management/commands
  copying build/lib/django/contrib/sitemaps/management/commands/ping_google.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps/management/commands
  creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates
  copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps/templates
  copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> build/bdist.linux-x86_64/wheel/./django/contrib/sitemaps/templates
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites
  copying build/lib/django/contrib/sites/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/admin.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/checks.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/management.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/managers.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/middleware.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/models.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/requests.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  copying build/lib/django/contrib/sites/shortcuts.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations
  copying build/lib/django/contrib/sites/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/migrations
  copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/migrations
  copying build/lib/django/contrib/sites/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/migrations
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/af/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/af/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ar/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ar/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ar_DZ/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ar_DZ/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ast/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ast/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/az/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/az/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/be/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/be/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/bg/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/bg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/bn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/bn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/br/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/br/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/bs/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/bs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ca/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ca/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ckb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ckb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/cs/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/cs/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/cy/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/cy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/da/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/da/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/de/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/de/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/dsb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/dsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/el/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/el/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/en/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/en/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/en_AU/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/en_AU/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/en_GB/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/en_GB/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/eo/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/eo/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_AR/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_AR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_CO/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_CO/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_MX/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_MX/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_VE/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/es_VE/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/et/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/et/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/eu/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/eu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fa/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fi/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fy/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/fy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ga/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ga/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/gd/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/gd/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/gl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/gl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/he/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/he/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hi/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hsb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hsb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hu/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hu/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hy/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/hy/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ia/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ia/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/id/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/id/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/io/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/io/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/is/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/is/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/it/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/it/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ja/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ja/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ka/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ka/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/kab/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/kab/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/kk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/kk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/km/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/km/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/kn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/kn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ko/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ko/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ky/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ky/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/lb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/lb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/lt/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/lt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/lv/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/lv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/mk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/mk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ml/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ml/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/mn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/mn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/mr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/mr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ms/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ms/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/my/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/my/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/nb/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/nb/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ne/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ne/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/nl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/nl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/nn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/nn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/os/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/os/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pa/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pa/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pt/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pt_BR/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/pt_BR/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ro/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ro/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ru/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ru/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sl/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sl/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sq/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sq/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sr_Latn/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sr_Latn/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sv/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sv/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sw/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/sw/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ta/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ta/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/te/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/te/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tg/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tg/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/th/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/th/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tr/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tr/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tt/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/tt/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/udm/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/udm/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/uk/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/uk/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ur/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/ur/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/uz/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/uz/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/vi/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/vi/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/zh_Hans/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/zh_Hans/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant
  creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/zh_Hant/LC_MESSAGES
  copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django/contrib/sites/locale/zh_Hant/LC_MESSAGES
  creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/checks.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/finders.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/handlers.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/storage.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/testing.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/urls.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/utils.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  copying build/lib/django/contrib/staticfiles/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles
  creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management
  copying build/lib/django/contrib/staticfiles/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles/management
  creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands
  copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles/management/commands
  copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles/management/commands
  copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles/management/commands
  copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> build/bdist.linux-x86_64/wheel/./django/contrib/staticfiles/management/commands
  creating build/bdist.linux-x86_64/wheel/django/contrib/syndication
  copying build/lib/django/contrib/syndication/__init__.py -> build/bdist.linux-x86_64/wheel/./django/contrib/syndication
  copying build/lib/django/contrib/syndication/apps.py -> build/bdist.linux-x86_64/wheel/./django/contrib/syndication
  copying build/lib/django/contrib/syndication/views.py -> build/bdist.linux-x86_64/wheel/./django/contrib/syndication
  creating build/bdist.linux-x86_64/wheel/django/core
  copying build/lib/django/core/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/asgi.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/exceptions.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/paginator.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/signals.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/signing.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/validators.py -> build/bdist.linux-x86_64/wheel/./django/core
  copying build/lib/django/core/wsgi.py -> build/bdist.linux-x86_64/wheel/./django/core
  creating build/bdist.linux-x86_64/wheel/django/core/cache
  copying build/lib/django/core/cache/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/cache
  copying build/lib/django/core/cache/utils.py -> build/bdist.linux-x86_64/wheel/./django/core/cache
  creating build/bdist.linux-x86_64/wheel/django/core/cache/backends
  copying build/lib/django/core/cache/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/base.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/db.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/dummy.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/filebased.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/locmem.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/memcached.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  copying build/lib/django/core/cache/backends/redis.py -> build/bdist.linux-x86_64/wheel/./django/core/cache/backends
  creating build/bdist.linux-x86_64/wheel/django/core/checks
  copying build/lib/django/core/checks/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/async_checks.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/caches.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/database.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/files.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/messages.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/model_checks.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/registry.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/templates.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/translation.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  copying build/lib/django/core/checks/urls.py -> build/bdist.linux-x86_64/wheel/./django/core/checks
  creating build/bdist.linux-x86_64/wheel/django/core/checks/compatibility
  copying build/lib/django/core/checks/compatibility/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/checks/compatibility
  copying build/lib/django/core/checks/compatibility/django_4_0.py -> build/bdist.linux-x86_64/wheel/./django/core/checks/compatibility
  creating build/bdist.linux-x86_64/wheel/django/core/checks/security
  copying build/lib/django/core/checks/security/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/checks/security
  copying build/lib/django/core/checks/security/base.py -> build/bdist.linux-x86_64/wheel/./django/core/checks/security
  copying build/lib/django/core/checks/security/csrf.py -> build/bdist.linux-x86_64/wheel/./django/core/checks/security
  copying build/lib/django/core/checks/security/sessions.py -> build/bdist.linux-x86_64/wheel/./django/core/checks/security
  creating build/bdist.linux-x86_64/wheel/django/core/files
  copying build/lib/django/core/files/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/base.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/images.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/locks.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/move.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/temp.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/uploadedfile.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/uploadhandler.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  copying build/lib/django/core/files/utils.py -> build/bdist.linux-x86_64/wheel/./django/core/files
  creating build/bdist.linux-x86_64/wheel/django/core/files/storage
  copying build/lib/django/core/files/storage/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/files/storage
  copying build/lib/django/core/files/storage/base.py -> build/bdist.linux-x86_64/wheel/./django/core/files/storage
  copying build/lib/django/core/files/storage/filesystem.py -> build/bdist.linux-x86_64/wheel/./django/core/files/storage
  copying build/lib/django/core/files/storage/handler.py -> build/bdist.linux-x86_64/wheel/./django/core/files/storage
  copying build/lib/django/core/files/storage/memory.py -> build/bdist.linux-x86_64/wheel/./django/core/files/storage
  copying build/lib/django/core/files/storage/mixins.py -> build/bdist.linux-x86_64/wheel/./django/core/files/storage
  creating build/bdist.linux-x86_64/wheel/django/core/handlers
  copying build/lib/django/core/handlers/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/handlers
  copying build/lib/django/core/handlers/asgi.py -> build/bdist.linux-x86_64/wheel/./django/core/handlers
  copying build/lib/django/core/handlers/base.py -> build/bdist.linux-x86_64/wheel/./django/core/handlers
  copying build/lib/django/core/handlers/exception.py -> build/bdist.linux-x86_64/wheel/./django/core/handlers
  copying build/lib/django/core/handlers/wsgi.py -> build/bdist.linux-x86_64/wheel/./django/core/handlers
  creating build/bdist.linux-x86_64/wheel/django/core/mail
  copying build/lib/django/core/mail/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/mail
  copying build/lib/django/core/mail/message.py -> build/bdist.linux-x86_64/wheel/./django/core/mail
  copying build/lib/django/core/mail/utils.py -> build/bdist.linux-x86_64/wheel/./django/core/mail
  creating build/bdist.linux-x86_64/wheel/django/core/mail/backends
  copying build/lib/django/core/mail/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  copying build/lib/django/core/mail/backends/base.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  copying build/lib/django/core/mail/backends/console.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  copying build/lib/django/core/mail/backends/dummy.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  copying build/lib/django/core/mail/backends/filebased.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  copying build/lib/django/core/mail/backends/locmem.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  copying build/lib/django/core/mail/backends/smtp.py -> build/bdist.linux-x86_64/wheel/./django/core/mail/backends
  creating build/bdist.linux-x86_64/wheel/django/core/management
  copying build/lib/django/core/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/management
  copying build/lib/django/core/management/base.py -> build/bdist.linux-x86_64/wheel/./django/core/management
  copying build/lib/django/core/management/color.py -> build/bdist.linux-x86_64/wheel/./django/core/management
  copying build/lib/django/core/management/sql.py -> build/bdist.linux-x86_64/wheel/./django/core/management
  copying build/lib/django/core/management/templates.py -> build/bdist.linux-x86_64/wheel/./django/core/management
  copying build/lib/django/core/management/utils.py -> build/bdist.linux-x86_64/wheel/./django/core/management
  creating build/bdist.linux-x86_64/wheel/django/core/management/commands
  copying build/lib/django/core/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/check.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/compilemessages.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/createcachetable.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/dbshell.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/diffsettings.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/dumpdata.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/flush.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/inspectdb.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/loaddata.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/makemessages.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/makemigrations.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/migrate.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/optimizemigration.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/runserver.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/sendtestemail.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/shell.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/showmigrations.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/sqlflush.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/sqlmigrate.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/sqlsequencereset.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/squashmigrations.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/startapp.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/startproject.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/test.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  copying build/lib/django/core/management/commands/testserver.py -> build/bdist.linux-x86_64/wheel/./django/core/management/commands
  creating build/bdist.linux-x86_64/wheel/django/core/serializers
  copying build/lib/django/core/serializers/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  copying build/lib/django/core/serializers/base.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  copying build/lib/django/core/serializers/json.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  copying build/lib/django/core/serializers/jsonl.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  copying build/lib/django/core/serializers/python.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  copying build/lib/django/core/serializers/pyyaml.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  copying build/lib/django/core/serializers/xml_serializer.py -> build/bdist.linux-x86_64/wheel/./django/core/serializers
  creating build/bdist.linux-x86_64/wheel/django/core/servers
  copying build/lib/django/core/servers/__init__.py -> build/bdist.linux-x86_64/wheel/./django/core/servers
  copying build/lib/django/core/servers/basehttp.py -> build/bdist.linux-x86_64/wheel/./django/core/servers
  creating build/bdist.linux-x86_64/wheel/django/db
  copying build/lib/django/db/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db
  copying build/lib/django/db/transaction.py -> build/bdist.linux-x86_64/wheel/./django/db
  copying build/lib/django/db/utils.py -> build/bdist.linux-x86_64/wheel/./django/db
  creating build/bdist.linux-x86_64/wheel/django/db/backends
  copying build/lib/django/db/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends
  copying build/lib/django/db/backends/ddl_references.py -> build/bdist.linux-x86_64/wheel/./django/db/backends
  copying build/lib/django/db/backends/signals.py -> build/bdist.linux-x86_64/wheel/./django/db/backends
  copying build/lib/django/db/backends/utils.py -> build/bdist.linux-x86_64/wheel/./django/db/backends
  creating build/bdist.linux-x86_64/wheel/django/db/backends/base
  copying build/lib/django/db/backends/base/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/base.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/client.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/creation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/features.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/introspection.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/operations.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/schema.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  copying build/lib/django/db/backends/base/validation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/base
  creating build/bdist.linux-x86_64/wheel/django/db/backends/dummy
  copying build/lib/django/db/backends/dummy/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/dummy
  copying build/lib/django/db/backends/dummy/base.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/dummy
  copying build/lib/django/db/backends/dummy/features.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/dummy
  creating build/bdist.linux-x86_64/wheel/django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/base.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/client.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/compiler.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/creation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/features.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/introspection.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/operations.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/schema.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  copying build/lib/django/db/backends/mysql/validation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/mysql
  creating build/bdist.linux-x86_64/wheel/django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/base.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/client.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/creation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/features.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/functions.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/introspection.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/operations.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/schema.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/utils.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  copying build/lib/django/db/backends/oracle/validation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/oracle
  creating build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/base.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/client.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/creation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/features.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/introspection.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/operations.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/psycopg_any.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  copying build/lib/django/db/backends/postgresql/schema.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/postgresql
  creating build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/_functions.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/base.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/client.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/creation.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/features.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/introspection.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/operations.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  copying build/lib/django/db/backends/sqlite3/schema.py -> build/bdist.linux-x86_64/wheel/./django/db/backends/sqlite3
  creating build/bdist.linux-x86_64/wheel/django/db/migrations
  copying build/lib/django/db/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/autodetector.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/exceptions.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/executor.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/graph.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/loader.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/migration.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/optimizer.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/questioner.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/recorder.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/serializer.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/state.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/utils.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  copying build/lib/django/db/migrations/writer.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations
  creating build/bdist.linux-x86_64/wheel/django/db/migrations/operations
  copying build/lib/django/db/migrations/operations/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations/operations
  copying build/lib/django/db/migrations/operations/base.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations/operations
  copying build/lib/django/db/migrations/operations/fields.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations/operations
  copying build/lib/django/db/migrations/operations/models.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations/operations
  copying build/lib/django/db/migrations/operations/special.py -> build/bdist.linux-x86_64/wheel/./django/db/migrations/operations
  creating build/bdist.linux-x86_64/wheel/django/db/models
  copying build/lib/django/db/models/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/aggregates.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/base.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/constants.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/constraints.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/deletion.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/enums.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/expressions.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/indexes.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/lookups.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/manager.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/options.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/query.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/query_utils.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/signals.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  copying build/lib/django/db/models/utils.py -> build/bdist.linux-x86_64/wheel/./django/db/models
  creating build/bdist.linux-x86_64/wheel/django/db/models/fields
  copying build/lib/django/db/models/fields/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/files.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/json.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/mixins.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/proxy.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/related.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/related_descriptors.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/related_lookups.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  copying build/lib/django/db/models/fields/reverse_related.py -> build/bdist.linux-x86_64/wheel/./django/db/models/fields
  creating build/bdist.linux-x86_64/wheel/django/db/models/functions
  copying build/lib/django/db/models/functions/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  copying build/lib/django/db/models/functions/comparison.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  copying build/lib/django/db/models/functions/datetime.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  copying build/lib/django/db/models/functions/math.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  copying build/lib/django/db/models/functions/mixins.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  copying build/lib/django/db/models/functions/text.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  copying build/lib/django/db/models/functions/window.py -> build/bdist.linux-x86_64/wheel/./django/db/models/functions
  creating build/bdist.linux-x86_64/wheel/django/db/models/sql
  copying build/lib/django/db/models/sql/__init__.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  copying build/lib/django/db/models/sql/compiler.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  copying build/lib/django/db/models/sql/constants.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  copying build/lib/django/db/models/sql/datastructures.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  copying build/lib/django/db/models/sql/query.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  copying build/lib/django/db/models/sql/subqueries.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  copying build/lib/django/db/models/sql/where.py -> build/bdist.linux-x86_64/wheel/./django/db/models/sql
  creating build/bdist.linux-x86_64/wheel/django/dispatch
  copying build/lib/django/dispatch/__init__.py -> build/bdist.linux-x86_64/wheel/./django/dispatch
  copying build/lib/django/dispatch/dispatcher.py -> build/bdist.linux-x86_64/wheel/./django/dispatch
  copying build/lib/django/dispatch/license.txt -> build/bdist.linux-x86_64/wheel/./django/dispatch
  creating build/bdist.linux-x86_64/wheel/django/forms
  copying build/lib/django/forms/__init__.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/boundfield.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/fields.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/forms.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/formsets.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/models.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/renderers.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/utils.py -> build/bdist.linux-x86_64/wheel/./django/forms
  copying build/lib/django/forms/widgets.py -> build/bdist.linux-x86_64/wheel/./django/forms
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/attrs.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/div.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/label.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/p.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/table.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  copying build/lib/django/forms/jinja2/django/forms/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict
  copying build/lib/django/forms/jinja2/django/forms/errors/dict/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/errors/dict
  copying build/lib/django/forms/jinja2/django/forms/errors/dict/text.txt -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/errors/dict
  copying build/lib/django/forms/jinja2/django/forms/errors/dict/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/errors/dict
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list
  copying build/lib/django/forms/jinja2/django/forms/errors/list/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/errors/list
  copying build/lib/django/forms/jinja2/django/forms/errors/list/text.txt -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/errors/list
  copying build/lib/django/forms/jinja2/django/forms/errors/list/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/errors/list
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
  copying build/lib/django/forms/jinja2/django/forms/formsets/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/formsets
  copying build/lib/django/forms/jinja2/django/forms/formsets/div.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/formsets
  copying build/lib/django/forms/jinja2/django/forms/formsets/p.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/formsets
  copying build/lib/django/forms/jinja2/django/forms/formsets/table.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/formsets
  copying build/lib/django/forms/jinja2/django/forms/formsets/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/formsets
  creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> build/bdist.linux-x86_64/wheel/./django/forms/jinja2/django/forms/widgets
  creating build/bdist.linux-x86_64/wheel/django/forms/templates
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/attrs.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/div.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/label.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/p.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/table.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  copying build/lib/django/forms/templates/django/forms/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict
  copying build/lib/django/forms/templates/django/forms/errors/dict/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/errors/dict
  copying build/lib/django/forms/templates/django/forms/errors/dict/text.txt -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/errors/dict
  copying build/lib/django/forms/templates/django/forms/errors/dict/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/errors/dict
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list
  copying build/lib/django/forms/templates/django/forms/errors/list/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/errors/list
  copying build/lib/django/forms/templates/django/forms/errors/list/text.txt -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/errors/list
  copying build/lib/django/forms/templates/django/forms/errors/list/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/errors/list
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
  copying build/lib/django/forms/templates/django/forms/formsets/default.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/formsets
  copying build/lib/django/forms/templates/django/forms/formsets/div.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/formsets
  copying build/lib/django/forms/templates/django/forms/formsets/p.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/formsets
  copying build/lib/django/forms/templates/django/forms/formsets/table.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/formsets
  copying build/lib/django/forms/templates/django/forms/formsets/ul.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/formsets
  creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/date.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/email.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/file.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/input.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/number.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/password.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/select.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/text.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/time.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  copying build/lib/django/forms/templates/django/forms/widgets/url.html -> build/bdist.linux-x86_64/wheel/./django/forms/templates/django/forms/widgets
  creating build/bdist.linux-x86_64/wheel/django/http
  copying build/lib/django/http/__init__.py -> build/bdist.linux-x86_64/wheel/./django/http
  copying build/lib/django/http/cookie.py -> build/bdist.linux-x86_64/wheel/./django/http
  copying build/lib/django/http/multipartparser.py -> build/bdist.linux-x86_64/wheel/./django/http
  copying build/lib/django/http/request.py -> build/bdist.linux-x86_64/wheel/./django/http
  copying build/lib/django/http/response.py -> build/bdist.linux-x86_64/wheel/./django/http
  creating build/bdist.linux-x86_64/wheel/django/middleware
  copying build/lib/django/middleware/__init__.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/cache.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/clickjacking.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/common.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/csrf.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/gzip.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/http.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/locale.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  copying build/lib/django/middleware/security.py -> build/bdist.linux-x86_64/wheel/./django/middleware
  creating build/bdist.linux-x86_64/wheel/django/template
  copying build/lib/django/template/__init__.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/autoreload.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/base.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/context.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/context_processors.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/defaultfilters.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/defaulttags.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/engine.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/exceptions.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/library.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/loader.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/loader_tags.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/response.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/smartif.py -> build/bdist.linux-x86_64/wheel/./django/template
  copying build/lib/django/template/utils.py -> build/bdist.linux-x86_64/wheel/./django/template
  creating build/bdist.linux-x86_64/wheel/django/template/backends
  copying build/lib/django/template/backends/__init__.py -> build/bdist.linux-x86_64/wheel/./django/template/backends
  copying build/lib/django/template/backends/base.py -> build/bdist.linux-x86_64/wheel/./django/template/backends
  copying build/lib/django/template/backends/django.py -> build/bdist.linux-x86_64/wheel/./django/template/backends
  copying build/lib/django/template/backends/dummy.py -> build/bdist.linux-x86_64/wheel/./django/template/backends
  copying build/lib/django/template/backends/jinja2.py -> build/bdist.linux-x86_64/wheel/./django/template/backends
  copying build/lib/django/template/backends/utils.py -> build/bdist.linux-x86_64/wheel/./django/template/backends
  creating build/bdist.linux-x86_64/wheel/django/template/loaders
  copying build/lib/django/template/loaders/__init__.py -> build/bdist.linux-x86_64/wheel/./django/template/loaders
  copying build/lib/django/template/loaders/app_directories.py -> build/bdist.linux-x86_64/wheel/./django/template/loaders
  copying build/lib/django/template/loaders/base.py -> build/bdist.linux-x86_64/wheel/./django/template/loaders
  copying build/lib/django/template/loaders/cached.py -> build/bdist.linux-x86_64/wheel/./django/template/loaders
  copying build/lib/django/template/loaders/filesystem.py -> build/bdist.linux-x86_64/wheel/./django/template/loaders
  copying build/lib/django/template/loaders/locmem.py -> build/bdist.linux-x86_64/wheel/./django/template/loaders
  creating build/bdist.linux-x86_64/wheel/django/templatetags
  copying build/lib/django/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/./django/templatetags
  copying build/lib/django/templatetags/cache.py -> build/bdist.linux-x86_64/wheel/./django/templatetags
  copying build/lib/django/templatetags/i18n.py -> build/bdist.linux-x86_64/wheel/./django/templatetags
  copying build/lib/django/templatetags/l10n.py -> build/bdist.linux-x86_64/wheel/./django/templatetags
  copying build/lib/django/templatetags/static.py -> build/bdist.linux-x86_64/wheel/./django/templatetags
  copying build/lib/django/templatetags/tz.py -> build/bdist.linux-x86_64/wheel/./django/templatetags
  creating build/bdist.linux-x86_64/wheel/django/test
  copying build/lib/django/test/__init__.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/client.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/html.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/runner.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/selenium.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/signals.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/testcases.py -> build/bdist.linux-x86_64/wheel/./django/test
  copying build/lib/django/test/utils.py -> build/bdist.linux-x86_64/wheel/./django/test
  creating build/bdist.linux-x86_64/wheel/django/urls
  copying build/lib/django/urls/__init__.py -> build/bdist.linux-x86_64/wheel/./django/urls
  copying build/lib/django/urls/base.py -> build/bdist.linux-x86_64/wheel/./django/urls
  copying build/lib/django/urls/conf.py -> build/bdist.linux-x86_64/wheel/./django/urls
  copying build/lib/django/urls/converters.py -> build/bdist.linux-x86_64/wheel/./django/urls
  copying build/lib/django/urls/exceptions.py -> build/bdist.linux-x86_64/wheel/./django/urls
  copying build/lib/django/urls/resolvers.py -> build/bdist.linux-x86_64/wheel/./django/urls
  copying build/lib/django/urls/utils.py -> build/bdist.linux-x86_64/wheel/./django/urls
  creating build/bdist.linux-x86_64/wheel/django/utils
  copying build/lib/django/utils/__init__.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/_os.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/archive.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/asyncio.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/autoreload.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/baseconv.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/cache.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/connection.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/crypto.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/datastructures.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/dateformat.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/dateparse.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/dates.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/datetime_safe.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/deconstruct.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/decorators.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/deprecation.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/duration.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/encoding.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/feedgenerator.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/formats.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/functional.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/hashable.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/html.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/http.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/inspect.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/ipv6.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/itercompat.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/jslex.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/log.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/lorem_ipsum.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/module_loading.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/numberformat.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/regex_helper.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/safestring.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/termcolors.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/text.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/timesince.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/timezone.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/topological_sort.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/tree.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/version.py -> build/bdist.linux-x86_64/wheel/./django/utils
  copying build/lib/django/utils/xmlutils.py -> build/bdist.linux-x86_64/wheel/./django/utils
  creating build/bdist.linux-x86_64/wheel/django/utils/translation
  copying build/lib/django/utils/translation/__init__.py -> build/bdist.linux-x86_64/wheel/./django/utils/translation
  copying build/lib/django/utils/translation/reloader.py -> build/bdist.linux-x86_64/wheel/./django/utils/translation
  copying build/lib/django/utils/translation/template.py -> build/bdist.linux-x86_64/wheel/./django/utils/translation
  copying build/lib/django/utils/translation/trans_null.py -> build/bdist.linux-x86_64/wheel/./django/utils/translation
  copying build/lib/django/utils/translation/trans_real.py -> build/bdist.linux-x86_64/wheel/./django/utils/translation
  creating build/bdist.linux-x86_64/wheel/django/views
  copying build/lib/django/views/__init__.py -> build/bdist.linux-x86_64/wheel/./django/views
  copying build/lib/django/views/csrf.py -> build/bdist.linux-x86_64/wheel/./django/views
  copying build/lib/django/views/debug.py -> build/bdist.linux-x86_64/wheel/./django/views
  copying build/lib/django/views/defaults.py -> build/bdist.linux-x86_64/wheel/./django/views
  copying build/lib/django/views/i18n.py -> build/bdist.linux-x86_64/wheel/./django/views
  copying build/lib/django/views/static.py -> build/bdist.linux-x86_64/wheel/./django/views
  creating build/bdist.linux-x86_64/wheel/django/views/decorators
  copying build/lib/django/views/decorators/__init__.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/cache.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/clickjacking.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/common.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/csrf.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/debug.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/gzip.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/http.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  copying build/lib/django/views/decorators/vary.py -> build/bdist.linux-x86_64/wheel/./django/views/decorators
  creating build/bdist.linux-x86_64/wheel/django/views/generic
  copying build/lib/django/views/generic/__init__.py -> build/bdist.linux-x86_64/wheel/./django/views/generic
  copying build/lib/django/views/generic/base.py -> build/bdist.linux-x86_64/wheel/./django/views/generic
  copying build/lib/django/views/generic/dates.py -> build/bdist.linux-x86_64/wheel/./django/views/generic
  copying build/lib/django/views/generic/detail.py -> build/bdist.linux-x86_64/wheel/./django/views/generic
  copying build/lib/django/views/generic/edit.py -> build/bdist.linux-x86_64/wheel/./django/views/generic
  copying build/lib/django/views/generic/list.py -> build/bdist.linux-x86_64/wheel/./django/views/generic
  creating build/bdist.linux-x86_64/wheel/django/views/templates
  copying build/lib/django/views/templates/default_urlconf.html -> build/bdist.linux-x86_64/wheel/./django/views/templates
  copying build/lib/django/views/templates/technical_404.html -> build/bdist.linux-x86_64/wheel/./django/views/templates
  copying build/lib/django/views/templates/technical_500.html -> build/bdist.linux-x86_64/wheel/./django/views/templates
  copying build/lib/django/views/templates/technical_500.txt -> build/bdist.linux-x86_64/wheel/./django/views/templates
  running install_egg_info
  Copying Django.egg-info to build/bdist.linux-x86_64/wheel/./Django-4.2.20-py3.13.egg-info
  running install_scripts
  creating build/bdist.linux-x86_64/wheel/django-4.2.20.dist-info/WHEEL
  creating '/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir/pip-wheel-mqctorp7/.tmp-mvx6egnn/django-4.2.20-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
  adding 'django/__init__.py'
  adding 'django/__main__.py'
  adding 'django/shortcuts.py'
  adding 'django/apps/__init__.py'
  adding 'django/apps/config.py'
  adding 'django/apps/registry.py'
  adding 'django/conf/__init__.py'
  adding 'django/conf/global_settings.py'
  adding 'django/conf/app_template/__init__.py-tpl'
  adding 'django/conf/app_template/admin.py-tpl'
  adding 'django/conf/app_template/apps.py-tpl'
  adding 'django/conf/app_template/models.py-tpl'
  adding 'django/conf/app_template/tests.py-tpl'
  adding 'django/conf/app_template/views.py-tpl'
  adding 'django/conf/app_template/migrations/__init__.py-tpl'
  adding 'django/conf/locale/__init__.py'
  adding 'django/conf/locale/af/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/af/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ar/__init__.py'
  adding 'django/conf/locale/ar/formats.py'
  adding 'django/conf/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ar/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ar_DZ/__init__.py'
  adding 'django/conf/locale/ar_DZ/formats.py'
  adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ast/LC_MESSAGES/django.po'
  adding 'django/conf/locale/az/__init__.py'
  adding 'django/conf/locale/az/formats.py'
  adding 'django/conf/locale/az/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/az/LC_MESSAGES/django.po'
  adding 'django/conf/locale/be/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/be/LC_MESSAGES/django.po'
  adding 'django/conf/locale/bg/__init__.py'
  adding 'django/conf/locale/bg/formats.py'
  adding 'django/conf/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/bg/LC_MESSAGES/django.po'
  adding 'django/conf/locale/bn/__init__.py'
  adding 'django/conf/locale/bn/formats.py'
  adding 'django/conf/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/bn/LC_MESSAGES/django.po'
  adding 'django/conf/locale/br/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/br/LC_MESSAGES/django.po'
  adding 'django/conf/locale/bs/__init__.py'
  adding 'django/conf/locale/bs/formats.py'
  adding 'django/conf/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/bs/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ca/__init__.py'
  adding 'django/conf/locale/ca/formats.py'
  adding 'django/conf/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ca/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ckb/__init__.py'
  adding 'django/conf/locale/ckb/formats.py'
  adding 'django/conf/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/conf/locale/cs/__init__.py'
  adding 'django/conf/locale/cs/formats.py'
  adding 'django/conf/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/cs/LC_MESSAGES/django.po'
  adding 'django/conf/locale/cy/__init__.py'
  adding 'django/conf/locale/cy/formats.py'
  adding 'django/conf/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/cy/LC_MESSAGES/django.po'
  adding 'django/conf/locale/da/__init__.py'
  adding 'django/conf/locale/da/formats.py'
  adding 'django/conf/locale/da/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/da/LC_MESSAGES/django.po'
  adding 'django/conf/locale/de/__init__.py'
  adding 'django/conf/locale/de/formats.py'
  adding 'django/conf/locale/de/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/de/LC_MESSAGES/django.po'
  adding 'django/conf/locale/de_CH/__init__.py'
  adding 'django/conf/locale/de_CH/formats.py'
  adding 'django/conf/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/conf/locale/el/__init__.py'
  adding 'django/conf/locale/el/formats.py'
  adding 'django/conf/locale/el/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/el/LC_MESSAGES/django.po'
  adding 'django/conf/locale/en/__init__.py'
  adding 'django/conf/locale/en/formats.py'
  adding 'django/conf/locale/en/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/en/LC_MESSAGES/django.po'
  adding 'django/conf/locale/en_AU/__init__.py'
  adding 'django/conf/locale/en_AU/formats.py'
  adding 'django/conf/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/conf/locale/en_GB/__init__.py'
  adding 'django/conf/locale/en_GB/formats.py'
  adding 'django/conf/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/conf/locale/eo/__init__.py'
  adding 'django/conf/locale/eo/formats.py'
  adding 'django/conf/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/eo/LC_MESSAGES/django.po'
  adding 'django/conf/locale/es/__init__.py'
  adding 'django/conf/locale/es/formats.py'
  adding 'django/conf/locale/es/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/es/LC_MESSAGES/django.po'
  adding 'django/conf/locale/es_AR/__init__.py'
  adding 'django/conf/locale/es_AR/formats.py'
  adding 'django/conf/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/conf/locale/es_CO/__init__.py'
  adding 'django/conf/locale/es_CO/formats.py'
  adding 'django/conf/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/conf/locale/es_MX/__init__.py'
  adding 'django/conf/locale/es_MX/formats.py'
  adding 'django/conf/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/conf/locale/es_NI/__init__.py'
  adding 'django/conf/locale/es_NI/formats.py'
  adding 'django/conf/locale/es_PR/__init__.py'
  adding 'django/conf/locale/es_PR/formats.py'
  adding 'django/conf/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/conf/locale/et/__init__.py'
  adding 'django/conf/locale/et/formats.py'
  adding 'django/conf/locale/et/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/et/LC_MESSAGES/django.po'
  adding 'django/conf/locale/eu/__init__.py'
  adding 'django/conf/locale/eu/formats.py'
  adding 'django/conf/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/eu/LC_MESSAGES/django.po'
  adding 'django/conf/locale/fa/__init__.py'
  adding 'django/conf/locale/fa/formats.py'
  adding 'django/conf/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/fa/LC_MESSAGES/django.po'
  adding 'django/conf/locale/fi/__init__.py'
  adding 'django/conf/locale/fi/formats.py'
  adding 'django/conf/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/fi/LC_MESSAGES/django.po'
  adding 'django/conf/locale/fr/__init__.py'
  adding 'django/conf/locale/fr/formats.py'
  adding 'django/conf/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/fr/LC_MESSAGES/django.po'
  adding 'django/conf/locale/fy/__init__.py'
  adding 'django/conf/locale/fy/formats.py'
  adding 'django/conf/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/fy/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ga/__init__.py'
  adding 'django/conf/locale/ga/formats.py'
  adding 'django/conf/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ga/LC_MESSAGES/django.po'
  adding 'django/conf/locale/gd/__init__.py'
  adding 'django/conf/locale/gd/formats.py'
  adding 'django/conf/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/gd/LC_MESSAGES/django.po'
  adding 'django/conf/locale/gl/__init__.py'
  adding 'django/conf/locale/gl/formats.py'
  adding 'django/conf/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/gl/LC_MESSAGES/django.po'
  adding 'django/conf/locale/he/__init__.py'
  adding 'django/conf/locale/he/formats.py'
  adding 'django/conf/locale/he/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/he/LC_MESSAGES/django.po'
  adding 'django/conf/locale/hi/__init__.py'
  adding 'django/conf/locale/hi/formats.py'
  adding 'django/conf/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/hi/LC_MESSAGES/django.po'
  adding 'django/conf/locale/hr/__init__.py'
  adding 'django/conf/locale/hr/formats.py'
  adding 'django/conf/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/hr/LC_MESSAGES/django.po'
  adding 'django/conf/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/conf/locale/hu/__init__.py'
  adding 'django/conf/locale/hu/formats.py'
  adding 'django/conf/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/hu/LC_MESSAGES/django.po'
  adding 'django/conf/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/hy/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ia/LC_MESSAGES/django.po'
  adding 'django/conf/locale/id/__init__.py'
  adding 'django/conf/locale/id/formats.py'
  adding 'django/conf/locale/id/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/id/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ig/__init__.py'
  adding 'django/conf/locale/ig/formats.py'
  adding 'django/conf/locale/ig/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ig/LC_MESSAGES/django.po'
  adding 'django/conf/locale/io/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/io/LC_MESSAGES/django.po'
  adding 'django/conf/locale/is/__init__.py'
  adding 'django/conf/locale/is/formats.py'
  adding 'django/conf/locale/is/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/is/LC_MESSAGES/django.po'
  adding 'django/conf/locale/it/__init__.py'
  adding 'django/conf/locale/it/formats.py'
  adding 'django/conf/locale/it/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/it/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ja/__init__.py'
  adding 'django/conf/locale/ja/formats.py'
  adding 'django/conf/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ja/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ka/__init__.py'
  adding 'django/conf/locale/ka/formats.py'
  adding 'django/conf/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ka/LC_MESSAGES/django.po'
  adding 'django/conf/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/kab/LC_MESSAGES/django.po'
  adding 'django/conf/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/kk/LC_MESSAGES/django.po'
  adding 'django/conf/locale/km/__init__.py'
  adding 'django/conf/locale/km/formats.py'
  adding 'django/conf/locale/km/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/km/LC_MESSAGES/django.po'
  adding 'django/conf/locale/kn/__init__.py'
  adding 'django/conf/locale/kn/formats.py'
  adding 'django/conf/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/kn/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ko/__init__.py'
  adding 'django/conf/locale/ko/formats.py'
  adding 'django/conf/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ko/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ky/__init__.py'
  adding 'django/conf/locale/ky/formats.py'
  adding 'django/conf/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ky/LC_MESSAGES/django.po'
  adding 'django/conf/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/lb/LC_MESSAGES/django.po'
  adding 'django/conf/locale/lt/__init__.py'
  adding 'django/conf/locale/lt/formats.py'
  adding 'django/conf/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/lt/LC_MESSAGES/django.po'
  adding 'django/conf/locale/lv/__init__.py'
  adding 'django/conf/locale/lv/formats.py'
  adding 'django/conf/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/lv/LC_MESSAGES/django.po'
  adding 'django/conf/locale/mk/__init__.py'
  adding 'django/conf/locale/mk/formats.py'
  adding 'django/conf/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/mk/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ml/__init__.py'
  adding 'django/conf/locale/ml/formats.py'
  adding 'django/conf/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ml/LC_MESSAGES/django.po'
  adding 'django/conf/locale/mn/__init__.py'
  adding 'django/conf/locale/mn/formats.py'
  adding 'django/conf/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/mn/LC_MESSAGES/django.po'
  adding 'django/conf/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/mr/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ms/__init__.py'
  adding 'django/conf/locale/ms/formats.py'
  adding 'django/conf/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ms/LC_MESSAGES/django.po'
  adding 'django/conf/locale/my/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/my/LC_MESSAGES/django.po'
  adding 'django/conf/locale/nb/__init__.py'
  adding 'django/conf/locale/nb/formats.py'
  adding 'django/conf/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/nb/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ne/LC_MESSAGES/django.po'
  adding 'django/conf/locale/nl/__init__.py'
  adding 'django/conf/locale/nl/formats.py'
  adding 'django/conf/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/nl/LC_MESSAGES/django.po'
  adding 'django/conf/locale/nn/__init__.py'
  adding 'django/conf/locale/nn/formats.py'
  adding 'django/conf/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/nn/LC_MESSAGES/django.po'
  adding 'django/conf/locale/os/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/os/LC_MESSAGES/django.po'
  adding 'django/conf/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/pa/LC_MESSAGES/django.po'
  adding 'django/conf/locale/pl/__init__.py'
  adding 'django/conf/locale/pl/formats.py'
  adding 'django/conf/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/pl/LC_MESSAGES/django.po'
  adding 'django/conf/locale/pt/__init__.py'
  adding 'django/conf/locale/pt/formats.py'
  adding 'django/conf/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/pt/LC_MESSAGES/django.po'
  adding 'django/conf/locale/pt_BR/__init__.py'
  adding 'django/conf/locale/pt_BR/formats.py'
  adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ro/__init__.py'
  adding 'django/conf/locale/ro/formats.py'
  adding 'django/conf/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ro/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ru/__init__.py'
  adding 'django/conf/locale/ru/formats.py'
  adding 'django/conf/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ru/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sk/__init__.py'
  adding 'django/conf/locale/sk/formats.py'
  adding 'django/conf/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sk/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sl/__init__.py'
  adding 'django/conf/locale/sl/formats.py'
  adding 'django/conf/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sl/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sq/__init__.py'
  adding 'django/conf/locale/sq/formats.py'
  adding 'django/conf/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sq/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sr/__init__.py'
  adding 'django/conf/locale/sr/formats.py'
  adding 'django/conf/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sr/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sr_Latn/__init__.py'
  adding 'django/conf/locale/sr_Latn/formats.py'
  adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sv/__init__.py'
  adding 'django/conf/locale/sv/formats.py'
  adding 'django/conf/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sv/LC_MESSAGES/django.po'
  adding 'django/conf/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/sw/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ta/__init__.py'
  adding 'django/conf/locale/ta/formats.py'
  adding 'django/conf/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ta/LC_MESSAGES/django.po'
  adding 'django/conf/locale/te/__init__.py'
  adding 'django/conf/locale/te/formats.py'
  adding 'django/conf/locale/te/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/te/LC_MESSAGES/django.po'
  adding 'django/conf/locale/tg/__init__.py'
  adding 'django/conf/locale/tg/formats.py'
  adding 'django/conf/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/tg/LC_MESSAGES/django.po'
  adding 'django/conf/locale/th/__init__.py'
  adding 'django/conf/locale/th/formats.py'
  adding 'django/conf/locale/th/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/th/LC_MESSAGES/django.po'
  adding 'django/conf/locale/tk/__init__.py'
  adding 'django/conf/locale/tk/formats.py'
  adding 'django/conf/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/tk/LC_MESSAGES/django.po'
  adding 'django/conf/locale/tr/__init__.py'
  adding 'django/conf/locale/tr/formats.py'
  adding 'django/conf/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/tr/LC_MESSAGES/django.po'
  adding 'django/conf/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/tt/LC_MESSAGES/django.po'
  adding 'django/conf/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/udm/LC_MESSAGES/django.po'
  adding 'django/conf/locale/uk/__init__.py'
  adding 'django/conf/locale/uk/formats.py'
  adding 'django/conf/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/uk/LC_MESSAGES/django.po'
  adding 'django/conf/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/ur/LC_MESSAGES/django.po'
  adding 'django/conf/locale/uz/__init__.py'
  adding 'django/conf/locale/uz/formats.py'
  adding 'django/conf/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/uz/LC_MESSAGES/django.po'
  adding 'django/conf/locale/vi/__init__.py'
  adding 'django/conf/locale/vi/formats.py'
  adding 'django/conf/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/vi/LC_MESSAGES/django.po'
  adding 'django/conf/locale/zh_Hans/__init__.py'
  adding 'django/conf/locale/zh_Hans/formats.py'
  adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/conf/locale/zh_Hant/__init__.py'
  adding 'django/conf/locale/zh_Hant/formats.py'
  adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/conf/project_template/manage.py-tpl'
  adding 'django/conf/project_template/project_name/__init__.py-tpl'
  adding 'django/conf/project_template/project_name/asgi.py-tpl'
  adding 'django/conf/project_template/project_name/settings.py-tpl'
  adding 'django/conf/project_template/project_name/urls.py-tpl'
  adding 'django/conf/project_template/project_name/wsgi.py-tpl'
  adding 'django/conf/urls/__init__.py'
  adding 'django/conf/urls/i18n.py'
  adding 'django/conf/urls/static.py'
  adding 'django/contrib/__init__.py'
  adding 'django/contrib/admin/__init__.py'
  adding 'django/contrib/admin/actions.py'
  adding 'django/contrib/admin/apps.py'
  adding 'django/contrib/admin/checks.py'
  adding 'django/contrib/admin/decorators.py'
  adding 'django/contrib/admin/exceptions.py'
  adding 'django/contrib/admin/filters.py'
  adding 'django/contrib/admin/forms.py'
  adding 'django/contrib/admin/helpers.py'
  adding 'django/contrib/admin/models.py'
  adding 'django/contrib/admin/options.py'
  adding 'django/contrib/admin/sites.py'
  adding 'django/contrib/admin/tests.py'
  adding 'django/contrib/admin/utils.py'
  adding 'django/contrib/admin/widgets.py'
  adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo'
  adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po'
  adding 'django/contrib/admin/migrations/0001_initial.py'
  adding 'django/contrib/admin/migrations/0002_logentry_remove_auto_add.py'
  adding 'django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py'
  adding 'django/contrib/admin/migrations/__init__.py'
  adding 'django/contrib/admin/static/admin/css/autocomplete.css'
  adding 'django/contrib/admin/static/admin/css/base.css'
  adding 'django/contrib/admin/static/admin/css/changelists.css'
  adding 'django/contrib/admin/static/admin/css/dark_mode.css'
  adding 'django/contrib/admin/static/admin/css/dashboard.css'
  adding 'django/contrib/admin/static/admin/css/forms.css'
  adding 'django/contrib/admin/static/admin/css/login.css'
  adding 'django/contrib/admin/static/admin/css/nav_sidebar.css'
  adding 'django/contrib/admin/static/admin/css/responsive.css'
  adding 'django/contrib/admin/static/admin/css/responsive_rtl.css'
  adding 'django/contrib/admin/static/admin/css/rtl.css'
  adding 'django/contrib/admin/static/admin/css/widgets.css'
  adding 'django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md'
  adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.css'
  adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.min.css'
  adding 'django/contrib/admin/static/admin/img/LICENSE'
  adding 'django/contrib/admin/static/admin/img/README.txt'
  adding 'django/contrib/admin/static/admin/img/calendar-icons.svg'
  adding 'django/contrib/admin/static/admin/img/icon-addlink.svg'
  adding 'django/contrib/admin/static/admin/img/icon-alert.svg'
  adding 'django/contrib/admin/static/admin/img/icon-calendar.svg'
  adding 'django/contrib/admin/static/admin/img/icon-changelink.svg'
  adding 'django/contrib/admin/static/admin/img/icon-clock.svg'
  adding 'django/contrib/admin/static/admin/img/icon-deletelink.svg'
  adding 'django/contrib/admin/static/admin/img/icon-no.svg'
  adding 'django/contrib/admin/static/admin/img/icon-unknown-alt.svg'
  adding 'django/contrib/admin/static/admin/img/icon-unknown.svg'
  adding 'django/contrib/admin/static/admin/img/icon-viewlink.svg'
  adding 'django/contrib/admin/static/admin/img/icon-yes.svg'
  adding 'django/contrib/admin/static/admin/img/inline-delete.svg'
  adding 'django/contrib/admin/static/admin/img/search.svg'
  adding 'django/contrib/admin/static/admin/img/selector-icons.svg'
  adding 'django/contrib/admin/static/admin/img/sorting-icons.svg'
  adding 'django/contrib/admin/static/admin/img/tooltag-add.svg'
  adding 'django/contrib/admin/static/admin/img/tooltag-arrowright.svg'
  adding 'django/contrib/admin/static/admin/img/gis/move_vertex_off.svg'
  adding 'django/contrib/admin/static/admin/img/gis/move_vertex_on.svg'
  adding 'django/contrib/admin/static/admin/js/SelectBox.js'
  adding 'django/contrib/admin/static/admin/js/SelectFilter2.js'
  adding 'django/contrib/admin/static/admin/js/actions.js'
  adding 'django/contrib/admin/static/admin/js/autocomplete.js'
  adding 'django/contrib/admin/static/admin/js/calendar.js'
  adding 'django/contrib/admin/static/admin/js/cancel.js'
  adding 'django/contrib/admin/static/admin/js/change_form.js'
  adding 'django/contrib/admin/static/admin/js/collapse.js'
  adding 'django/contrib/admin/static/admin/js/core.js'
  adding 'django/contrib/admin/static/admin/js/filters.js'
  adding 'django/contrib/admin/static/admin/js/inlines.js'
  adding 'django/contrib/admin/static/admin/js/jquery.init.js'
  adding 'django/contrib/admin/static/admin/js/nav_sidebar.js'
  adding 'django/contrib/admin/static/admin/js/popup_response.js'
  adding 'django/contrib/admin/static/admin/js/prepopulate.js'
  adding 'django/contrib/admin/static/admin/js/prepopulate_init.js'
  adding 'django/contrib/admin/static/admin/js/theme.js'
  adding 'django/contrib/admin/static/admin/js/urlify.js'
  adding 'django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js'
  adding 'django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js'
  adding 'django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt'
  adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.js'
  adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js'
  adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js'
  adding 'django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt'
  adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js'
  adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js'
  adding 'django/contrib/admin/templates/admin/404.html'
  adding 'django/contrib/admin/templates/admin/500.html'
  adding 'django/contrib/admin/templates/admin/actions.html'
  adding 'django/contrib/admin/templates/admin/app_index.html'
  adding 'django/contrib/admin/templates/admin/app_list.html'
  adding 'django/contrib/admin/templates/admin/base.html'
  adding 'django/contrib/admin/templates/admin/base_site.html'
  adding 'django/contrib/admin/templates/admin/change_form.html'
  adding 'django/contrib/admin/templates/admin/change_form_object_tools.html'
  adding 'django/contrib/admin/templates/admin/change_list.html'
  adding 'django/contrib/admin/templates/admin/change_list_object_tools.html'
  adding 'django/contrib/admin/templates/admin/change_list_results.html'
  adding 'django/contrib/admin/templates/admin/color_theme_toggle.html'
  adding 'django/contrib/admin/templates/admin/date_hierarchy.html'
  adding 'django/contrib/admin/templates/admin/delete_confirmation.html'
  adding 'django/contrib/admin/templates/admin/delete_selected_confirmation.html'
  adding 'django/contrib/admin/templates/admin/filter.html'
  adding 'django/contrib/admin/templates/admin/index.html'
  adding 'django/contrib/admin/templates/admin/invalid_setup.html'
  adding 'django/contrib/admin/templates/admin/login.html'
  adding 'django/contrib/admin/templates/admin/nav_sidebar.html'
  adding 'django/contrib/admin/templates/admin/object_history.html'
  adding 'django/contrib/admin/templates/admin/pagination.html'
  adding 'django/contrib/admin/templates/admin/popup_response.html'
  adding 'django/contrib/admin/templates/admin/prepopulated_fields_js.html'
  adding 'django/contrib/admin/templates/admin/search_form.html'
  adding 'django/contrib/admin/templates/admin/submit_line.html'
  adding 'django/contrib/admin/templates/admin/auth/user/add_form.html'
  adding 'django/contrib/admin/templates/admin/auth/user/change_password.html'
  adding 'django/contrib/admin/templates/admin/edit_inline/stacked.html'
  adding 'django/contrib/admin/templates/admin/edit_inline/tabular.html'
  adding 'django/contrib/admin/templates/admin/includes/fieldset.html'
  adding 'django/contrib/admin/templates/admin/includes/object_delete_summary.html'
  adding 'django/contrib/admin/templates/admin/widgets/clearable_file_input.html'
  adding 'django/contrib/admin/templates/admin/widgets/date.html'
  adding 'django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html'
  adding 'django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html'
  adding 'django/contrib/admin/templates/admin/widgets/radio.html'
  adding 'django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html'
  adding 'django/contrib/admin/templates/admin/widgets/split_datetime.html'
  adding 'django/contrib/admin/templates/admin/widgets/time.html'
  adding 'django/contrib/admin/templates/admin/widgets/url.html'
  adding 'django/contrib/admin/templates/registration/logged_out.html'
  adding 'django/contrib/admin/templates/registration/password_change_done.html'
  adding 'django/contrib/admin/templates/registration/password_change_form.html'
  adding 'django/contrib/admin/templates/registration/password_reset_complete.html'
  adding 'django/contrib/admin/templates/registration/password_reset_confirm.html'
  adding 'django/contrib/admin/templates/registration/password_reset_done.html'
  adding 'django/contrib/admin/templates/registration/password_reset_email.html'
  adding 'django/contrib/admin/templates/registration/password_reset_form.html'
  adding 'django/contrib/admin/templatetags/__init__.py'
  adding 'django/contrib/admin/templatetags/admin_list.py'
  adding 'django/contrib/admin/templatetags/admin_modify.py'
  adding 'django/contrib/admin/templatetags/admin_urls.py'
  adding 'django/contrib/admin/templatetags/base.py'
  adding 'django/contrib/admin/templatetags/log.py'
  adding 'django/contrib/admin/views/__init__.py'
  adding 'django/contrib/admin/views/autocomplete.py'
  adding 'django/contrib/admin/views/decorators.py'
  adding 'django/contrib/admin/views/main.py'
  adding 'django/contrib/admindocs/__init__.py'
  adding 'django/contrib/admindocs/apps.py'
  adding 'django/contrib/admindocs/middleware.py'
  adding 'django/contrib/admindocs/urls.py'
  adding 'django/contrib/admindocs/utils.py'
  adding 'django/contrib/admindocs/views.py'
  adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/admindocs/templates/admin_doc/bookmarklets.html'
  adding 'django/contrib/admindocs/templates/admin_doc/index.html'
  adding 'django/contrib/admindocs/templates/admin_doc/missing_docutils.html'
  adding 'django/contrib/admindocs/templates/admin_doc/model_detail.html'
  adding 'django/contrib/admindocs/templates/admin_doc/model_index.html'
  adding 'django/contrib/admindocs/templates/admin_doc/template_detail.html'
  adding 'django/contrib/admindocs/templates/admin_doc/template_filter_index.html'
  adding 'django/contrib/admindocs/templates/admin_doc/template_tag_index.html'
  adding 'django/contrib/admindocs/templates/admin_doc/view_detail.html'
  adding 'django/contrib/admindocs/templates/admin_doc/view_index.html'
  adding 'django/contrib/auth/__init__.py'
  adding 'django/contrib/auth/admin.py'
  adding 'django/contrib/auth/apps.py'
  adding 'django/contrib/auth/backends.py'
  adding 'django/contrib/auth/base_user.py'
  adding 'django/contrib/auth/checks.py'
  adding 'django/contrib/auth/common-passwords.txt.gz'
  adding 'django/contrib/auth/context_processors.py'
  adding 'django/contrib/auth/decorators.py'
  adding 'django/contrib/auth/forms.py'
  adding 'django/contrib/auth/hashers.py'
  adding 'django/contrib/auth/middleware.py'
  adding 'django/contrib/auth/mixins.py'
  adding 'django/contrib/auth/models.py'
  adding 'django/contrib/auth/password_validation.py'
  adding 'django/contrib/auth/signals.py'
  adding 'django/contrib/auth/tokens.py'
  adding 'django/contrib/auth/urls.py'
  adding 'django/contrib/auth/validators.py'
  adding 'django/contrib/auth/views.py'
  adding 'django/contrib/auth/handlers/__init__.py'
  adding 'django/contrib/auth/handlers/modwsgi.py'
  adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/auth/management/__init__.py'
  adding 'django/contrib/auth/management/commands/__init__.py'
  adding 'django/contrib/auth/management/commands/changepassword.py'
  adding 'django/contrib/auth/management/commands/createsuperuser.py'
  adding 'django/contrib/auth/migrations/0001_initial.py'
  adding 'django/contrib/auth/migrations/0002_alter_permission_name_max_length.py'
  adding 'django/contrib/auth/migrations/0003_alter_user_email_max_length.py'
  adding 'django/contrib/auth/migrations/0004_alter_user_username_opts.py'
  adding 'django/contrib/auth/migrations/0005_alter_user_last_login_null.py'
  adding 'django/contrib/auth/migrations/0006_require_contenttypes_0002.py'
  adding 'django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py'
  adding 'django/contrib/auth/migrations/0008_alter_user_username_max_length.py'
  adding 'django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py'
  adding 'django/contrib/auth/migrations/0010_alter_group_name_max_length.py'
  adding 'django/contrib/auth/migrations/0011_update_proxy_permissions.py'
  adding 'django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py'
  adding 'django/contrib/auth/migrations/__init__.py'
  adding 'django/contrib/auth/templates/auth/widgets/read_only_password_hash.html'
  adding 'django/contrib/auth/templates/registration/password_reset_subject.txt'
  adding 'django/contrib/contenttypes/__init__.py'
  adding 'django/contrib/contenttypes/admin.py'
  adding 'django/contrib/contenttypes/apps.py'
  adding 'django/contrib/contenttypes/checks.py'
  adding 'django/contrib/contenttypes/fields.py'
  adding 'django/contrib/contenttypes/forms.py'
  adding 'django/contrib/contenttypes/models.py'
  adding 'django/contrib/contenttypes/views.py'
  adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/contenttypes/management/__init__.py'
  adding 'django/contrib/contenttypes/management/commands/__init__.py'
  adding 'django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py'
  adding 'django/contrib/contenttypes/migrations/0001_initial.py'
  adding 'django/contrib/contenttypes/migrations/0002_remove_content_type_name.py'
  adding 'django/contrib/contenttypes/migrations/__init__.py'
  adding 'django/contrib/flatpages/__init__.py'
  adding 'django/contrib/flatpages/admin.py'
  adding 'django/contrib/flatpages/apps.py'
  adding 'django/contrib/flatpages/forms.py'
  adding 'django/contrib/flatpages/middleware.py'
  adding 'django/contrib/flatpages/models.py'
  adding 'django/contrib/flatpages/sitemaps.py'
  adding 'django/contrib/flatpages/urls.py'
  adding 'django/contrib/flatpages/views.py'
  adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/flatpages/migrations/0001_initial.py'
  adding 'django/contrib/flatpages/migrations/__init__.py'
  adding 'django/contrib/flatpages/templatetags/__init__.py'
  adding 'django/contrib/flatpages/templatetags/flatpages.py'
  adding 'django/contrib/gis/__init__.py'
  adding 'django/contrib/gis/apps.py'
  adding 'django/contrib/gis/feeds.py'
  adding 'django/contrib/gis/geometry.py'
  adding 'django/contrib/gis/measure.py'
  adding 'django/contrib/gis/ptr.py'
  adding 'django/contrib/gis/shortcuts.py'
  adding 'django/contrib/gis/views.py'
  adding 'django/contrib/gis/admin/__init__.py'
  adding 'django/contrib/gis/admin/options.py'
  adding 'django/contrib/gis/admin/widgets.py'
  adding 'django/contrib/gis/db/__init__.py'
  adding 'django/contrib/gis/db/backends/__init__.py'
  adding 'django/contrib/gis/db/backends/utils.py'
  adding 'django/contrib/gis/db/backends/base/__init__.py'
  adding 'django/contrib/gis/db/backends/base/adapter.py'
  adding 'django/contrib/gis/db/backends/base/features.py'
  adding 'django/contrib/gis/db/backends/base/models.py'
  adding 'django/contrib/gis/db/backends/base/operations.py'
  adding 'django/contrib/gis/db/backends/mysql/__init__.py'
  adding 'django/contrib/gis/db/backends/mysql/base.py'
  adding 'django/contrib/gis/db/backends/mysql/features.py'
  adding 'django/contrib/gis/db/backends/mysql/introspection.py'
  adding 'django/contrib/gis/db/backends/mysql/operations.py'
  adding 'django/contrib/gis/db/backends/mysql/schema.py'
  adding 'django/contrib/gis/db/backends/oracle/__init__.py'
  adding 'django/contrib/gis/db/backends/oracle/adapter.py'
  adding 'django/contrib/gis/db/backends/oracle/base.py'
  adding 'django/contrib/gis/db/backends/oracle/features.py'
  adding 'django/contrib/gis/db/backends/oracle/introspection.py'
  adding 'django/contrib/gis/db/backends/oracle/models.py'
  adding 'django/contrib/gis/db/backends/oracle/operations.py'
  adding 'django/contrib/gis/db/backends/oracle/schema.py'
  adding 'django/contrib/gis/db/backends/postgis/__init__.py'
  adding 'django/contrib/gis/db/backends/postgis/adapter.py'
  adding 'django/contrib/gis/db/backends/postgis/base.py'
  adding 'django/contrib/gis/db/backends/postgis/const.py'
  adding 'django/contrib/gis/db/backends/postgis/features.py'
  adding 'django/contrib/gis/db/backends/postgis/introspection.py'
  adding 'django/contrib/gis/db/backends/postgis/models.py'
  adding 'django/contrib/gis/db/backends/postgis/operations.py'
  adding 'django/contrib/gis/db/backends/postgis/pgraster.py'
  adding 'django/contrib/gis/db/backends/postgis/schema.py'
  adding 'django/contrib/gis/db/backends/spatialite/__init__.py'
  adding 'django/contrib/gis/db/backends/spatialite/adapter.py'
  adding 'django/contrib/gis/db/backends/spatialite/base.py'
  adding 'django/contrib/gis/db/backends/spatialite/client.py'
  adding 'django/contrib/gis/db/backends/spatialite/features.py'
  adding 'django/contrib/gis/db/backends/spatialite/introspection.py'
  adding 'django/contrib/gis/db/backends/spatialite/models.py'
  adding 'django/contrib/gis/db/backends/spatialite/operations.py'
  adding 'django/contrib/gis/db/backends/spatialite/schema.py'
  adding 'django/contrib/gis/db/models/__init__.py'
  adding 'django/contrib/gis/db/models/aggregates.py'
  adding 'django/contrib/gis/db/models/fields.py'
  adding 'django/contrib/gis/db/models/functions.py'
  adding 'django/contrib/gis/db/models/lookups.py'
  adding 'django/contrib/gis/db/models/proxy.py'
  adding 'django/contrib/gis/db/models/sql/__init__.py'
  adding 'django/contrib/gis/db/models/sql/conversion.py'
  adding 'django/contrib/gis/forms/__init__.py'
  adding 'django/contrib/gis/forms/fields.py'
  adding 'django/contrib/gis/forms/widgets.py'
  adding 'django/contrib/gis/gdal/LICENSE'
  adding 'django/contrib/gis/gdal/__init__.py'
  adding 'django/contrib/gis/gdal/base.py'
  adding 'django/contrib/gis/gdal/datasource.py'
  adding 'django/contrib/gis/gdal/driver.py'
  adding 'django/contrib/gis/gdal/envelope.py'
  adding 'django/contrib/gis/gdal/error.py'
  adding 'django/contrib/gis/gdal/feature.py'
  adding 'django/contrib/gis/gdal/field.py'
  adding 'django/contrib/gis/gdal/geometries.py'
  adding 'django/contrib/gis/gdal/geomtype.py'
  adding 'django/contrib/gis/gdal/layer.py'
  adding 'django/contrib/gis/gdal/libgdal.py'
  adding 'django/contrib/gis/gdal/srs.py'
  adding 'django/contrib/gis/gdal/prototypes/__init__.py'
  adding 'django/contrib/gis/gdal/prototypes/ds.py'
  adding 'django/contrib/gis/gdal/prototypes/errcheck.py'
  adding 'django/contrib/gis/gdal/prototypes/generation.py'
  adding 'django/contrib/gis/gdal/prototypes/geom.py'
  adding 'django/contrib/gis/gdal/prototypes/raster.py'
  adding 'django/contrib/gis/gdal/prototypes/srs.py'
  adding 'django/contrib/gis/gdal/raster/__init__.py'
  adding 'django/contrib/gis/gdal/raster/band.py'
  adding 'django/contrib/gis/gdal/raster/base.py'
  adding 'django/contrib/gis/gdal/raster/const.py'
  adding 'django/contrib/gis/gdal/raster/source.py'
  adding 'django/contrib/gis/geoip2/__init__.py'
  adding 'django/contrib/gis/geoip2/base.py'
  adding 'django/contrib/gis/geoip2/resources.py'
  adding 'django/contrib/gis/geos/LICENSE'
  adding 'django/contrib/gis/geos/__init__.py'
  adding 'django/contrib/gis/geos/base.py'
  adding 'django/contrib/gis/geos/collections.py'
  adding 'django/contrib/gis/geos/coordseq.py'
  adding 'django/contrib/gis/geos/error.py'
  adding 'django/contrib/gis/geos/factory.py'
  adding 'django/contrib/gis/geos/geometry.py'
  adding 'django/contrib/gis/geos/io.py'
  adding 'django/contrib/gis/geos/libgeos.py'
  adding 'django/contrib/gis/geos/linestring.py'
  adding 'django/contrib/gis/geos/mutable_list.py'
  adding 'django/contrib/gis/geos/point.py'
  adding 'django/contrib/gis/geos/polygon.py'
  adding 'django/contrib/gis/geos/prepared.py'
  adding 'django/contrib/gis/geos/prototypes/__init__.py'
  adding 'django/contrib/gis/geos/prototypes/coordseq.py'
  adding 'django/contrib/gis/geos/prototypes/errcheck.py'
  adding 'django/contrib/gis/geos/prototypes/geom.py'
  adding 'django/contrib/gis/geos/prototypes/io.py'
  adding 'django/contrib/gis/geos/prototypes/misc.py'
  adding 'django/contrib/gis/geos/prototypes/predicates.py'
  adding 'django/contrib/gis/geos/prototypes/prepared.py'
  adding 'django/contrib/gis/geos/prototypes/threadsafe.py'
  adding 'django/contrib/gis/geos/prototypes/topology.py'
  adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/gis/management/__init__.py'
  adding 'django/contrib/gis/management/commands/__init__.py'
  adding 'django/contrib/gis/management/commands/inspectdb.py'
  adding 'django/contrib/gis/management/commands/ogrinspect.py'
  adding 'django/contrib/gis/serializers/__init__.py'
  adding 'django/contrib/gis/serializers/geojson.py'
  adding 'django/contrib/gis/sitemaps/__init__.py'
  adding 'django/contrib/gis/sitemaps/kml.py'
  adding 'django/contrib/gis/sitemaps/views.py'
  adding 'django/contrib/gis/static/gis/css/ol3.css'
  adding 'django/contrib/gis/static/gis/img/draw_line_off.svg'
  adding 'django/contrib/gis/static/gis/img/draw_line_on.svg'
  adding 'django/contrib/gis/static/gis/img/draw_point_off.svg'
  adding 'django/contrib/gis/static/gis/img/draw_point_on.svg'
  adding 'django/contrib/gis/static/gis/img/draw_polygon_off.svg'
  adding 'django/contrib/gis/static/gis/img/draw_polygon_on.svg'
  adding 'django/contrib/gis/static/gis/js/OLMapWidget.js'
  adding 'django/contrib/gis/templates/gis/openlayers-osm.html'
  adding 'django/contrib/gis/templates/gis/openlayers.html'
  adding 'django/contrib/gis/templates/gis/admin/openlayers.html'
  adding 'django/contrib/gis/templates/gis/admin/openlayers.js'
  adding 'django/contrib/gis/templates/gis/admin/osm.html'
  adding 'django/contrib/gis/templates/gis/admin/osm.js'
  adding 'django/contrib/gis/templates/gis/kml/base.kml'
  adding 'django/contrib/gis/templates/gis/kml/placemarks.kml'
  adding 'django/contrib/gis/utils/__init__.py'
  adding 'django/contrib/gis/utils/layermapping.py'
  adding 'django/contrib/gis/utils/ogrinfo.py'
  adding 'django/contrib/gis/utils/ogrinspect.py'
  adding 'django/contrib/gis/utils/srs.py'
  adding 'django/contrib/humanize/__init__.py'
  adding 'django/contrib/humanize/apps.py'
  adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/humanize/templatetags/__init__.py'
  adding 'django/contrib/humanize/templatetags/humanize.py'
  adding 'django/contrib/messages/__init__.py'
  adding 'django/contrib/messages/api.py'
  adding 'django/contrib/messages/apps.py'
  adding 'django/contrib/messages/constants.py'
  adding 'django/contrib/messages/context_processors.py'
  adding 'django/contrib/messages/middleware.py'
  adding 'django/contrib/messages/utils.py'
  adding 'django/contrib/messages/views.py'
  adding 'django/contrib/messages/storage/__init__.py'
  adding 'django/contrib/messages/storage/base.py'
  adding 'django/contrib/messages/storage/cookie.py'
  adding 'django/contrib/messages/storage/fallback.py'
  adding 'django/contrib/messages/storage/session.py'
  adding 'django/contrib/postgres/__init__.py'
  adding 'django/contrib/postgres/apps.py'
  adding 'django/contrib/postgres/constraints.py'
  adding 'django/contrib/postgres/expressions.py'
  adding 'django/contrib/postgres/functions.py'
  adding 'django/contrib/postgres/indexes.py'
  adding 'django/contrib/postgres/lookups.py'
  adding 'django/contrib/postgres/operations.py'
  adding 'django/contrib/postgres/search.py'
  adding 'django/contrib/postgres/serializers.py'
  adding 'django/contrib/postgres/signals.py'
  adding 'django/contrib/postgres/utils.py'
  adding 'django/contrib/postgres/validators.py'
  adding 'django/contrib/postgres/aggregates/__init__.py'
  adding 'django/contrib/postgres/aggregates/general.py'
  adding 'django/contrib/postgres/aggregates/mixins.py'
  adding 'django/contrib/postgres/aggregates/statistics.py'
  adding 'django/contrib/postgres/fields/__init__.py'
  adding 'django/contrib/postgres/fields/array.py'
  adding 'django/contrib/postgres/fields/citext.py'
  adding 'django/contrib/postgres/fields/hstore.py'
  adding 'django/contrib/postgres/fields/jsonb.py'
  adding 'django/contrib/postgres/fields/ranges.py'
  adding 'django/contrib/postgres/fields/utils.py'
  adding 'django/contrib/postgres/forms/__init__.py'
  adding 'django/contrib/postgres/forms/array.py'
  adding 'django/contrib/postgres/forms/hstore.py'
  adding 'django/contrib/postgres/forms/ranges.py'
  adding 'django/contrib/postgres/jinja2/postgres/widgets/split_array.html'
  adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/postgres/templates/postgres/widgets/split_array.html'
  adding 'django/contrib/redirects/__init__.py'
  adding 'django/contrib/redirects/admin.py'
  adding 'django/contrib/redirects/apps.py'
  adding 'django/contrib/redirects/middleware.py'
  adding 'django/contrib/redirects/models.py'
  adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/redirects/migrations/0001_initial.py'
  adding 'django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py'
  adding 'django/contrib/redirects/migrations/__init__.py'
  adding 'django/contrib/sessions/__init__.py'
  adding 'django/contrib/sessions/apps.py'
  adding 'django/contrib/sessions/base_session.py'
  adding 'django/contrib/sessions/exceptions.py'
  adding 'django/contrib/sessions/middleware.py'
  adding 'django/contrib/sessions/models.py'
  adding 'django/contrib/sessions/serializers.py'
  adding 'django/contrib/sessions/backends/__init__.py'
  adding 'django/contrib/sessions/backends/base.py'
  adding 'django/contrib/sessions/backends/cache.py'
  adding 'django/contrib/sessions/backends/cached_db.py'
  adding 'django/contrib/sessions/backends/db.py'
  adding 'django/contrib/sessions/backends/file.py'
  adding 'django/contrib/sessions/backends/signed_cookies.py'
  adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/sessions/management/__init__.py'
  adding 'django/contrib/sessions/management/commands/__init__.py'
  adding 'django/contrib/sessions/management/commands/clearsessions.py'
  adding 'django/contrib/sessions/migrations/0001_initial.py'
  adding 'django/contrib/sessions/migrations/__init__.py'
  adding 'django/contrib/sitemaps/__init__.py'
  adding 'django/contrib/sitemaps/apps.py'
  adding 'django/contrib/sitemaps/views.py'
  adding 'django/contrib/sitemaps/management/__init__.py'
  adding 'django/contrib/sitemaps/management/commands/__init__.py'
  adding 'django/contrib/sitemaps/management/commands/ping_google.py'
  adding 'django/contrib/sitemaps/templates/sitemap.xml'
  adding 'django/contrib/sitemaps/templates/sitemap_index.xml'
  adding 'django/contrib/sites/__init__.py'
  adding 'django/contrib/sites/admin.py'
  adding 'django/contrib/sites/apps.py'
  adding 'django/contrib/sites/checks.py'
  adding 'django/contrib/sites/management.py'
  adding 'django/contrib/sites/managers.py'
  adding 'django/contrib/sites/middleware.py'
  adding 'django/contrib/sites/models.py'
  adding 'django/contrib/sites/requests.py'
  adding 'django/contrib/sites/shortcuts.py'
  adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo'
  adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po'
  adding 'django/contrib/sites/migrations/0001_initial.py'
  adding 'django/contrib/sites/migrations/0002_alter_domain_unique.py'
  adding 'django/contrib/sites/migrations/__init__.py'
  adding 'django/contrib/staticfiles/__init__.py'
  adding 'django/contrib/staticfiles/apps.py'
  adding 'django/contrib/staticfiles/checks.py'
  adding 'django/contrib/staticfiles/finders.py'
  adding 'django/contrib/staticfiles/handlers.py'
  adding 'django/contrib/staticfiles/storage.py'
  adding 'django/contrib/staticfiles/testing.py'
  adding 'django/contrib/staticfiles/urls.py'
  adding 'django/contrib/staticfiles/utils.py'
  adding 'django/contrib/staticfiles/views.py'
  adding 'django/contrib/staticfiles/management/__init__.py'
  adding 'django/contrib/staticfiles/management/commands/__init__.py'
  adding 'django/contrib/staticfiles/management/commands/collectstatic.py'
  adding 'django/contrib/staticfiles/management/commands/findstatic.py'
  adding 'django/contrib/staticfiles/management/commands/runserver.py'
  adding 'django/contrib/syndication/__init__.py'
  adding 'django/contrib/syndication/apps.py'
  adding 'django/contrib/syndication/views.py'
  adding 'django/core/__init__.py'
  adding 'django/core/asgi.py'
  adding 'django/core/exceptions.py'
  adding 'django/core/paginator.py'
  adding 'django/core/signals.py'
  adding 'django/core/signing.py'
  adding 'django/core/validators.py'
  adding 'django/core/wsgi.py'
  adding 'django/core/cache/__init__.py'
  adding 'django/core/cache/utils.py'
  adding 'django/core/cache/backends/__init__.py'
  adding 'django/core/cache/backends/base.py'
  adding 'django/core/cache/backends/db.py'
  adding 'django/core/cache/backends/dummy.py'
  adding 'django/core/cache/backends/filebased.py'
  adding 'django/core/cache/backends/locmem.py'
  adding 'django/core/cache/backends/memcached.py'
  adding 'django/core/cache/backends/redis.py'
  adding 'django/core/checks/__init__.py'
  adding 'django/core/checks/async_checks.py'
  adding 'django/core/checks/caches.py'
  adding 'django/core/checks/database.py'
  adding 'django/core/checks/files.py'
  adding 'django/core/checks/messages.py'
  adding 'django/core/checks/model_checks.py'
  adding 'django/core/checks/registry.py'
  adding 'django/core/checks/templates.py'
  adding 'django/core/checks/translation.py'
  adding 'django/core/checks/urls.py'
  adding 'django/core/checks/compatibility/__init__.py'
  adding 'django/core/checks/compatibility/django_4_0.py'
  adding 'django/core/checks/security/__init__.py'
  adding 'django/core/checks/security/base.py'
  adding 'django/core/checks/security/csrf.py'
  adding 'django/core/checks/security/sessions.py'
  adding 'django/core/files/__init__.py'
  adding 'django/core/files/base.py'
  adding 'django/core/files/images.py'
  adding 'django/core/files/locks.py'
  adding 'django/core/files/move.py'
  adding 'django/core/files/temp.py'
  adding 'django/core/files/uploadedfile.py'
  adding 'django/core/files/uploadhandler.py'
  adding 'django/core/files/utils.py'
  adding 'django/core/files/storage/__init__.py'
  adding 'django/core/files/storage/base.py'
  adding 'django/core/files/storage/filesystem.py'
  adding 'django/core/files/storage/handler.py'
  adding 'django/core/files/storage/memory.py'
  adding 'django/core/files/storage/mixins.py'
  adding 'django/core/handlers/__init__.py'
  adding 'django/core/handlers/asgi.py'
  adding 'django/core/handlers/base.py'
  adding 'django/core/handlers/exception.py'
  adding 'django/core/handlers/wsgi.py'
  adding 'django/core/mail/__init__.py'
  adding 'django/core/mail/message.py'
  adding 'django/core/mail/utils.py'
  adding 'django/core/mail/backends/__init__.py'
  adding 'django/core/mail/backends/base.py'
  adding 'django/core/mail/backends/console.py'
  adding 'django/core/mail/backends/dummy.py'
  adding 'django/core/mail/backends/filebased.py'
  adding 'django/core/mail/backends/locmem.py'
  adding 'django/core/mail/backends/smtp.py'
  adding 'django/core/management/__init__.py'
  adding 'django/core/management/base.py'
  adding 'django/core/management/color.py'
  adding 'django/core/management/sql.py'
  adding 'django/core/management/templates.py'
  adding 'django/core/management/utils.py'
  adding 'django/core/management/commands/__init__.py'
  adding 'django/core/management/commands/check.py'
  adding 'django/core/management/commands/compilemessages.py'
  adding 'django/core/management/commands/createcachetable.py'
  adding 'django/core/management/commands/dbshell.py'
  adding 'django/core/management/commands/diffsettings.py'
  adding 'django/core/management/commands/dumpdata.py'
  adding 'django/core/management/commands/flush.py'
  adding 'django/core/management/commands/inspectdb.py'
  adding 'django/core/management/commands/loaddata.py'
  adding 'django/core/management/commands/makemessages.py'
  adding 'django/core/management/commands/makemigrations.py'
  adding 'django/core/management/commands/migrate.py'
  adding 'django/core/management/commands/optimizemigration.py'
  adding 'django/core/management/commands/runserver.py'
  adding 'django/core/management/commands/sendtestemail.py'
  adding 'django/core/management/commands/shell.py'
  adding 'django/core/management/commands/showmigrations.py'
  adding 'django/core/management/commands/sqlflush.py'
  adding 'django/core/management/commands/sqlmigrate.py'
  adding 'django/core/management/commands/sqlsequencereset.py'
  adding 'django/core/management/commands/squashmigrations.py'
  adding 'django/core/management/commands/startapp.py'
  adding 'django/core/management/commands/startproject.py'
  adding 'django/core/management/commands/test.py'
  adding 'django/core/management/commands/testserver.py'
  adding 'django/core/serializers/__init__.py'
  adding 'django/core/serializers/base.py'
  adding 'django/core/serializers/json.py'
  adding 'django/core/serializers/jsonl.py'
  adding 'django/core/serializers/python.py'
  adding 'django/core/serializers/pyyaml.py'
  adding 'django/core/serializers/xml_serializer.py'
  adding 'django/core/servers/__init__.py'
  adding 'django/core/servers/basehttp.py'
  adding 'django/db/__init__.py'
  adding 'django/db/transaction.py'
  adding 'django/db/utils.py'
  adding 'django/db/backends/__init__.py'
  adding 'django/db/backends/ddl_references.py'
  adding 'django/db/backends/signals.py'
  adding 'django/db/backends/utils.py'
  adding 'django/db/backends/base/__init__.py'
  adding 'django/db/backends/base/base.py'
  adding 'django/db/backends/base/client.py'
  adding 'django/db/backends/base/creation.py'
  adding 'django/db/backends/base/features.py'
  adding 'django/db/backends/base/introspection.py'
  adding 'django/db/backends/base/operations.py'
  adding 'django/db/backends/base/schema.py'
  adding 'django/db/backends/base/validation.py'
  adding 'django/db/backends/dummy/__init__.py'
  adding 'django/db/backends/dummy/base.py'
  adding 'django/db/backends/dummy/features.py'
  adding 'django/db/backends/mysql/__init__.py'
  adding 'django/db/backends/mysql/base.py'
  adding 'django/db/backends/mysql/client.py'
  adding 'django/db/backends/mysql/compiler.py'
  adding 'django/db/backends/mysql/creation.py'
  adding 'django/db/backends/mysql/features.py'
  adding 'django/db/backends/mysql/introspection.py'
  adding 'django/db/backends/mysql/operations.py'
  adding 'django/db/backends/mysql/schema.py'
  adding 'django/db/backends/mysql/validation.py'
  adding 'django/db/backends/oracle/__init__.py'
  adding 'django/db/backends/oracle/base.py'
  adding 'django/db/backends/oracle/client.py'
  adding 'django/db/backends/oracle/creation.py'
  adding 'django/db/backends/oracle/features.py'
  adding 'django/db/backends/oracle/functions.py'
  adding 'django/db/backends/oracle/introspection.py'
  adding 'django/db/backends/oracle/operations.py'
  adding 'django/db/backends/oracle/schema.py'
  adding 'django/db/backends/oracle/utils.py'
  adding 'django/db/backends/oracle/validation.py'
  adding 'django/db/backends/postgresql/__init__.py'
  adding 'django/db/backends/postgresql/base.py'
  adding 'django/db/backends/postgresql/client.py'
  adding 'django/db/backends/postgresql/creation.py'
  adding 'django/db/backends/postgresql/features.py'
  adding 'django/db/backends/postgresql/introspection.py'
  adding 'django/db/backends/postgresql/operations.py'
  adding 'django/db/backends/postgresql/psycopg_any.py'
  adding 'django/db/backends/postgresql/schema.py'
  adding 'django/db/backends/sqlite3/__init__.py'
  adding 'django/db/backends/sqlite3/_functions.py'
  adding 'django/db/backends/sqlite3/base.py'
  adding 'django/db/backends/sqlite3/client.py'
  adding 'django/db/backends/sqlite3/creation.py'
  adding 'django/db/backends/sqlite3/features.py'
  adding 'django/db/backends/sqlite3/introspection.py'
  adding 'django/db/backends/sqlite3/operations.py'
  adding 'django/db/backends/sqlite3/schema.py'
  adding 'django/db/migrations/__init__.py'
  adding 'django/db/migrations/autodetector.py'
  adding 'django/db/migrations/exceptions.py'
  adding 'django/db/migrations/executor.py'
  adding 'django/db/migrations/graph.py'
  adding 'django/db/migrations/loader.py'
  adding 'django/db/migrations/migration.py'
  adding 'django/db/migrations/optimizer.py'
  adding 'django/db/migrations/questioner.py'
  adding 'django/db/migrations/recorder.py'
  adding 'django/db/migrations/serializer.py'
  adding 'django/db/migrations/state.py'
  adding 'django/db/migrations/utils.py'
  adding 'django/db/migrations/writer.py'
  adding 'django/db/migrations/operations/__init__.py'
  adding 'django/db/migrations/operations/base.py'
  adding 'django/db/migrations/operations/fields.py'
  adding 'django/db/migrations/operations/models.py'
  adding 'django/db/migrations/operations/special.py'
  adding 'django/db/models/__init__.py'
  adding 'django/db/models/aggregates.py'
  adding 'django/db/models/base.py'
  adding 'django/db/models/constants.py'
  adding 'django/db/models/constraints.py'
  adding 'django/db/models/deletion.py'
  adding 'django/db/models/enums.py'
  adding 'django/db/models/expressions.py'
  adding 'django/db/models/indexes.py'
  adding 'django/db/models/lookups.py'
  adding 'django/db/models/manager.py'
  adding 'django/db/models/options.py'
  adding 'django/db/models/query.py'
  adding 'django/db/models/query_utils.py'
  adding 'django/db/models/signals.py'
  adding 'django/db/models/utils.py'
  adding 'django/db/models/fields/__init__.py'
  adding 'django/db/models/fields/files.py'
  adding 'django/db/models/fields/json.py'
  adding 'django/db/models/fields/mixins.py'
  adding 'django/db/models/fields/proxy.py'
  adding 'django/db/models/fields/related.py'
  adding 'django/db/models/fields/related_descriptors.py'
  adding 'django/db/models/fields/related_lookups.py'
  adding 'django/db/models/fields/reverse_related.py'
  adding 'django/db/models/functions/__init__.py'
  adding 'django/db/models/functions/comparison.py'
  adding 'django/db/models/functions/datetime.py'
  adding 'django/db/models/functions/math.py'
  adding 'django/db/models/functions/mixins.py'
  adding 'django/db/models/functions/text.py'
  adding 'django/db/models/functions/window.py'
  adding 'django/db/models/sql/__init__.py'
  adding 'django/db/models/sql/compiler.py'
  adding 'django/db/models/sql/constants.py'
  adding 'django/db/models/sql/datastructures.py'
  adding 'django/db/models/sql/query.py'
  adding 'django/db/models/sql/subqueries.py'
  adding 'django/db/models/sql/where.py'
  adding 'django/dispatch/__init__.py'
  adding 'django/dispatch/dispatcher.py'
  adding 'django/dispatch/license.txt'
  adding 'django/forms/__init__.py'
  adding 'django/forms/boundfield.py'
  adding 'django/forms/fields.py'
  adding 'django/forms/forms.py'
  adding 'django/forms/formsets.py'
  adding 'django/forms/models.py'
  adding 'django/forms/renderers.py'
  adding 'django/forms/utils.py'
  adding 'django/forms/widgets.py'
  adding 'django/forms/jinja2/django/forms/attrs.html'
  adding 'django/forms/jinja2/django/forms/default.html'
  adding 'django/forms/jinja2/django/forms/div.html'
  adding 'django/forms/jinja2/django/forms/label.html'
  adding 'django/forms/jinja2/django/forms/p.html'
  adding 'django/forms/jinja2/django/forms/table.html'
  adding 'django/forms/jinja2/django/forms/ul.html'
  adding 'django/forms/jinja2/django/forms/errors/dict/default.html'
  adding 'django/forms/jinja2/django/forms/errors/dict/text.txt'
  adding 'django/forms/jinja2/django/forms/errors/dict/ul.html'
  adding 'django/forms/jinja2/django/forms/errors/list/default.html'
  adding 'django/forms/jinja2/django/forms/errors/list/text.txt'
  adding 'django/forms/jinja2/django/forms/errors/list/ul.html'
  adding 'django/forms/jinja2/django/forms/formsets/default.html'
  adding 'django/forms/jinja2/django/forms/formsets/div.html'
  adding 'django/forms/jinja2/django/forms/formsets/p.html'
  adding 'django/forms/jinja2/django/forms/formsets/table.html'
  adding 'django/forms/jinja2/django/forms/formsets/ul.html'
  adding 'django/forms/jinja2/django/forms/widgets/attrs.html'
  adding 'django/forms/jinja2/django/forms/widgets/checkbox.html'
  adding 'django/forms/jinja2/django/forms/widgets/checkbox_option.html'
  adding 'django/forms/jinja2/django/forms/widgets/checkbox_select.html'
  adding 'django/forms/jinja2/django/forms/widgets/clearable_file_input.html'
  adding 'django/forms/jinja2/django/forms/widgets/date.html'
  adding 'django/forms/jinja2/django/forms/widgets/datetime.html'
  adding 'django/forms/jinja2/django/forms/widgets/email.html'
  adding 'django/forms/jinja2/django/forms/widgets/file.html'
  adding 'django/forms/jinja2/django/forms/widgets/hidden.html'
  adding 'django/forms/jinja2/django/forms/widgets/input.html'
  adding 'django/forms/jinja2/django/forms/widgets/input_option.html'
  adding 'django/forms/jinja2/django/forms/widgets/multiple_hidden.html'
  adding 'django/forms/jinja2/django/forms/widgets/multiple_input.html'
  adding 'django/forms/jinja2/django/forms/widgets/multiwidget.html'
  adding 'django/forms/jinja2/django/forms/widgets/number.html'
  adding 'django/forms/jinja2/django/forms/widgets/password.html'
  adding 'django/forms/jinja2/django/forms/widgets/radio.html'
  adding 'django/forms/jinja2/django/forms/widgets/radio_option.html'
  adding 'django/forms/jinja2/django/forms/widgets/select.html'
  adding 'django/forms/jinja2/django/forms/widgets/select_date.html'
  adding 'django/forms/jinja2/django/forms/widgets/select_option.html'
  adding 'django/forms/jinja2/django/forms/widgets/splitdatetime.html'
  adding 'django/forms/jinja2/django/forms/widgets/splithiddendatetime.html'
  adding 'django/forms/jinja2/django/forms/widgets/text.html'
  adding 'django/forms/jinja2/django/forms/widgets/textarea.html'
  adding 'django/forms/jinja2/django/forms/widgets/time.html'
  adding 'django/forms/jinja2/django/forms/widgets/url.html'
  adding 'django/forms/templates/django/forms/attrs.html'
  adding 'django/forms/templates/django/forms/default.html'
  adding 'django/forms/templates/django/forms/div.html'
  adding 'django/forms/templates/django/forms/label.html'
  adding 'django/forms/templates/django/forms/p.html'
  adding 'django/forms/templates/django/forms/table.html'
  adding 'django/forms/templates/django/forms/ul.html'
  adding 'django/forms/templates/django/forms/errors/dict/default.html'
  adding 'django/forms/templates/django/forms/errors/dict/text.txt'
  adding 'django/forms/templates/django/forms/errors/dict/ul.html'
  adding 'django/forms/templates/django/forms/errors/list/default.html'
  adding 'django/forms/templates/django/forms/errors/list/text.txt'
  adding 'django/forms/templates/django/forms/errors/list/ul.html'
  adding 'django/forms/templates/django/forms/formsets/default.html'
  adding 'django/forms/templates/django/forms/formsets/div.html'
  adding 'django/forms/templates/django/forms/formsets/p.html'
  adding 'django/forms/templates/django/forms/formsets/table.html'
  adding 'django/forms/templates/django/forms/formsets/ul.html'
  adding 'django/forms/templates/django/forms/widgets/attrs.html'
  adding 'django/forms/templates/django/forms/widgets/checkbox.html'
  adding 'django/forms/templates/django/forms/widgets/checkbox_option.html'
  adding 'django/forms/templates/django/forms/widgets/checkbox_select.html'
  adding 'django/forms/templates/django/forms/widgets/clearable_file_input.html'
  adding 'django/forms/templates/django/forms/widgets/date.html'
  adding 'django/forms/templates/django/forms/widgets/datetime.html'
  adding 'django/forms/templates/django/forms/widgets/email.html'
  adding 'django/forms/templates/django/forms/widgets/file.html'
  adding 'django/forms/templates/django/forms/widgets/hidden.html'
  adding 'django/forms/templates/django/forms/widgets/input.html'
  adding 'django/forms/templates/django/forms/widgets/input_option.html'
  adding 'django/forms/templates/django/forms/widgets/multiple_hidden.html'
  adding 'django/forms/templates/django/forms/widgets/multiple_input.html'
  adding 'django/forms/templates/django/forms/widgets/multiwidget.html'
  adding 'django/forms/templates/django/forms/widgets/number.html'
  adding 'django/forms/templates/django/forms/widgets/password.html'
  adding 'django/forms/templates/django/forms/widgets/radio.html'
  adding 'django/forms/templates/django/forms/widgets/radio_option.html'
  adding 'django/forms/templates/django/forms/widgets/select.html'
  adding 'django/forms/templates/django/forms/widgets/select_date.html'
  adding 'django/forms/templates/django/forms/widgets/select_option.html'
  adding 'django/forms/templates/django/forms/widgets/splitdatetime.html'
  adding 'django/forms/templates/django/forms/widgets/splithiddendatetime.html'
  adding 'django/forms/templates/django/forms/widgets/text.html'
  adding 'django/forms/templates/django/forms/widgets/textarea.html'
  adding 'django/forms/templates/django/forms/widgets/time.html'
  adding 'django/forms/templates/django/forms/widgets/url.html'
  adding 'django/http/__init__.py'
  adding 'django/http/cookie.py'
  adding 'django/http/multipartparser.py'
  adding 'django/http/request.py'
  adding 'django/http/response.py'
  adding 'django/middleware/__init__.py'
  adding 'django/middleware/cache.py'
  adding 'django/middleware/clickjacking.py'
  adding 'django/middleware/common.py'
  adding 'django/middleware/csrf.py'
  adding 'django/middleware/gzip.py'
  adding 'django/middleware/http.py'
  adding 'django/middleware/locale.py'
  adding 'django/middleware/security.py'
  adding 'django/template/__init__.py'
  adding 'django/template/autoreload.py'
  adding 'django/template/base.py'
  adding 'django/template/context.py'
  adding 'django/template/context_processors.py'
  adding 'django/template/defaultfilters.py'
  adding 'django/template/defaulttags.py'
  adding 'django/template/engine.py'
  adding 'django/template/exceptions.py'
  adding 'django/template/library.py'
  adding 'django/template/loader.py'
  adding 'django/template/loader_tags.py'
  adding 'django/template/response.py'
  adding 'django/template/smartif.py'
  adding 'django/template/utils.py'
  adding 'django/template/backends/__init__.py'
  adding 'django/template/backends/base.py'
  adding 'django/template/backends/django.py'
  adding 'django/template/backends/dummy.py'
  adding 'django/template/backends/jinja2.py'
  adding 'django/template/backends/utils.py'
  adding 'django/template/loaders/__init__.py'
  adding 'django/template/loaders/app_directories.py'
  adding 'django/template/loaders/base.py'
  adding 'django/template/loaders/cached.py'
  adding 'django/template/loaders/filesystem.py'
  adding 'django/template/loaders/locmem.py'
  adding 'django/templatetags/__init__.py'
  adding 'django/templatetags/cache.py'
  adding 'django/templatetags/i18n.py'
  adding 'django/templatetags/l10n.py'
  adding 'django/templatetags/static.py'
  adding 'django/templatetags/tz.py'
  adding 'django/test/__init__.py'
  adding 'django/test/client.py'
  adding 'django/test/html.py'
  adding 'django/test/runner.py'
  adding 'django/test/selenium.py'
  adding 'django/test/signals.py'
  adding 'django/test/testcases.py'
  adding 'django/test/utils.py'
  adding 'django/urls/__init__.py'
  adding 'django/urls/base.py'
  adding 'django/urls/conf.py'
  adding 'django/urls/converters.py'
  adding 'django/urls/exceptions.py'
  adding 'django/urls/resolvers.py'
  adding 'django/urls/utils.py'
  adding 'django/utils/__init__.py'
  adding 'django/utils/_os.py'
  adding 'django/utils/archive.py'
  adding 'django/utils/asyncio.py'
  adding 'django/utils/autoreload.py'
  adding 'django/utils/baseconv.py'
  adding 'django/utils/cache.py'
  adding 'django/utils/connection.py'
  adding 'django/utils/crypto.py'
  adding 'django/utils/datastructures.py'
  adding 'django/utils/dateformat.py'
  adding 'django/utils/dateparse.py'
  adding 'django/utils/dates.py'
  adding 'django/utils/datetime_safe.py'
  adding 'django/utils/deconstruct.py'
  adding 'django/utils/decorators.py'
  adding 'django/utils/deprecation.py'
  adding 'django/utils/duration.py'
  adding 'django/utils/encoding.py'
  adding 'django/utils/feedgenerator.py'
  adding 'django/utils/formats.py'
  adding 'django/utils/functional.py'
  adding 'django/utils/hashable.py'
  adding 'django/utils/html.py'
  adding 'django/utils/http.py'
  adding 'django/utils/inspect.py'
  adding 'django/utils/ipv6.py'
  adding 'django/utils/itercompat.py'
  adding 'django/utils/jslex.py'
  adding 'django/utils/log.py'
  adding 'django/utils/lorem_ipsum.py'
  adding 'django/utils/module_loading.py'
  adding 'django/utils/numberformat.py'
  adding 'django/utils/regex_helper.py'
  adding 'django/utils/safestring.py'
  adding 'django/utils/termcolors.py'
  adding 'django/utils/text.py'
  adding 'django/utils/timesince.py'
  adding 'django/utils/timezone.py'
  adding 'django/utils/topological_sort.py'
  adding 'django/utils/tree.py'
  adding 'django/utils/version.py'
  adding 'django/utils/xmlutils.py'
  adding 'django/utils/translation/__init__.py'
  adding 'django/utils/translation/reloader.py'
  adding 'django/utils/translation/template.py'
  adding 'django/utils/translation/trans_null.py'
  adding 'django/utils/translation/trans_real.py'
  adding 'django/views/__init__.py'
  adding 'django/views/csrf.py'
  adding 'django/views/debug.py'
  adding 'django/views/defaults.py'
  adding 'django/views/i18n.py'
  adding 'django/views/static.py'
  adding 'django/views/decorators/__init__.py'
  adding 'django/views/decorators/cache.py'
  adding 'django/views/decorators/clickjacking.py'
  adding 'django/views/decorators/common.py'
  adding 'django/views/decorators/csrf.py'
  adding 'django/views/decorators/debug.py'
  adding 'django/views/decorators/gzip.py'
  adding 'django/views/decorators/http.py'
  adding 'django/views/decorators/vary.py'
  adding 'django/views/generic/__init__.py'
  adding 'django/views/generic/base.py'
  adding 'django/views/generic/dates.py'
  adding 'django/views/generic/detail.py'
  adding 'django/views/generic/edit.py'
  adding 'django/views/generic/list.py'
  adding 'django/views/templates/default_urlconf.html'
  adding 'django/views/templates/technical_404.html'
  adding 'django/views/templates/technical_500.html'
  adding 'django/views/templates/technical_500.txt'
  adding 'django-4.2.20.dist-info/licenses/AUTHORS'
  adding 'django-4.2.20.dist-info/licenses/LICENSE'
  adding 'django-4.2.20.dist-info/licenses/LICENSE.python'
  adding 'django-4.2.20.dist-info/METADATA'
  adding 'django-4.2.20.dist-info/WHEEL'
  adding 'django-4.2.20.dist-info/entry_points.txt'
  adding 'django-4.2.20.dist-info/top_level.txt'
  adding 'django-4.2.20.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Building wheel for Django (pyproject.toml): finished with status 'done'
  Created wheel for Django: filename=django-4.2.20-py3-none-any.whl size=8054411 sha256=5faa330159083c220b392e17ddcd8c48e2469fbf870249144f5589d311f857c6
  Stored in directory: /builddir/.cache/pip/wheels/7b/8d/fe/565d674076ba0124e3532589bf5eae758dd9fe95a2029f54c4
Successfully built Django
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.XzLcDM
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ '[' /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT '!=' / ']'
+ rm -rf /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT
++ dirname /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build
+ mkdir /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd Django-4.2.20
++ ls /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir/django-4.2.20-py3-none-any.whl
++ xargs basename --multiple
++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/'
+ specifier=django==4.2.20
+ '[' -z django==4.2.20 ']'
+ TMPDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/.pyproject-builddir
+ /usr/bin/python3 -m pip install --root /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir django==4.2.20
Using pip 25.1.1 from /usr/lib/python3.13/site-packages/pip (python 3.13)
Looking in links: /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/pyproject-wheeldir
Processing ./pyproject-wheeldir/django-4.2.20-py3-none-any.whl
Installing collected packages: django
  Creating /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin
  changing mode of /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/django-admin to 755
Successfully installed django-4.2.20
+ '[' -d /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin ']'
+ '[' -z sP ']'
+ shebang_flags=-kasP
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pathfix.py -pni /usr/bin/python3 -kasP /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/django-admin
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/django-admin: updating
+ rm -rfv /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/__pycache__
+ rm -f /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-ghost-distinfo
+ site_dirs=()
+ '[' -d /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages ']'
+ site_dirs+=("/usr/lib/python3.13/site-packages")
+ '[' /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib64/python3.13/site-packages '!=' /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages ']'
+ '[' -d /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib64/python3.13/site-packages ']'
+ for site_dir in ${site_dirs[@]}
+ for distinfo in /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT$site_dir/*.dist-info
+ echo '%ghost /usr/lib/python3.13/site-packages/django-4.2.20.dist-info'
+ sed -i s/pip/rpm/ /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django-4.2.20.dist-info/INSTALLER
+ PYTHONPATH=/usr/lib/rpm/redhat
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT --record /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django-4.2.20.dist-info/RECORD --output /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-record
+ rm -fv /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django-4.2.20.dist-info/RECORD
removed '/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django-4.2.20.dist-info/RECORD'
+ rm -fv /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django-4.2.20.dist-info/REQUESTED
removed '/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django-4.2.20.dist-info/REQUESTED'
++ wc -l /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-ghost-distinfo
++ cut -f1 '-d '
+ lines=1
+ '[' 1 -ne 1 ']'
+ RPM_FILES_ESCAPE=4.19
+ /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-files --output-modules /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-modules --buildroot /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT --sitelib /usr/lib/python3.13/site-packages --sitearch /usr/lib64/python3.13/site-packages --python-version 3.13 --pyproject-record /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-record --prefix /usr django
+ cd docs
+ mkdir djangohtml
+ mkdir -p _build/doctrees _build/html
+ make html
sphinx-build -b djangohtml -n -d _build/doctrees -D language=en   . _build/html
Running Sphinx v8.2.3
loading translations [en]... done
Converting `source_suffix = '.txt'` to `source_suffix = {'.txt': 'restructuredtext'}`.
loading intersphinx inventory 'python' from https://docs.python.org/3/objects.inv ...
loading intersphinx inventory 'sphinx' from https://www.sphinx-doc.org/en/master/objects.inv ...
loading intersphinx inventory 'psycopg' from https://www.psycopg.org/psycopg3/docs/objects.inv ...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to <class 'requests.exceptions.ConnectionError'>: HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f1246e64d70>: Failed to resolve 'docs.python.org' ([Errno -3] Temporary failure in name resolution)"))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://www.psycopg.org/psycopg3/docs/objects.inv' not fetchable due to <class 'requests.exceptions.ConnectionError'>: HTTPSConnectionPool(host='www.psycopg.org', port=443): Max retries exceeded with url: /psycopg3/docs/objects.inv (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f1246e4afd0>: Failed to resolve 'www.psycopg.org' ([Errno -3] Temporary failure in name resolution)"))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://www.sphinx-doc.org/en/master/objects.inv' not fetchable due to <class 'requests.exceptions.ConnectionError'>: HTTPSConnectionPool(host='www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/objects.inv (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f1246e4aad0>: Failed to resolve 'www.sphinx-doc.org' ([Errno -3] Temporary failure in name resolution)"))
building [mo]: targets for 0 po files that are out of date
writing output... 
building [djangohtml]: targets for 590 source files that are out of date
updating environment: [new config] 590 added, 0 changed, 0 removed
reading sources... [  0%] contents
reading sources... [  0%] faq/admin
reading sources... [  1%] faq/contributing
reading sources... [  1%] faq/general
reading sources... [  1%] faq/help
reading sources... [  1%] faq/index
reading sources... [  1%] faq/install
reading sources... [  1%] faq/models
reading sources... [  2%] faq/troubleshooting
reading sources... [  2%] faq/usage
reading sources... [  2%] glossary
reading sources... [  2%] howto/auth-remote-user
reading sources... [  2%] howto/csrf
reading sources... [  2%] howto/custom-file-storage
reading sources... [  3%] howto/custom-lookups
reading sources... [  3%] howto/custom-management-commands
reading sources... [  3%] howto/custom-model-fields
reading sources... [  3%] howto/custom-template-backend
reading sources... [  3%] howto/custom-template-tags
reading sources... [  3%] howto/delete-app
reading sources... [  4%] howto/deployment/asgi/daphne
reading sources... [  4%] howto/deployment/asgi/hypercorn
reading sources... [  4%] howto/deployment/asgi/index
reading sources... [  4%] howto/deployment/asgi/uvicorn
reading sources... [  4%] howto/deployment/checklist
reading sources... [  4%] howto/deployment/index
reading sources... [  5%] howto/deployment/wsgi/apache-auth
reading sources... [  5%] howto/deployment/wsgi/gunicorn
reading sources... [  5%] howto/deployment/wsgi/index
reading sources... [  5%] howto/deployment/wsgi/modwsgi
reading sources... [  5%] howto/deployment/wsgi/uwsgi
reading sources... [  5%] howto/error-reporting
reading sources... [  6%] howto/index
reading sources... [  6%] howto/initial-data
reading sources... [  6%] howto/legacy-databases
reading sources... [  6%] howto/logging
reading sources... [  6%] howto/outputting-csv
reading sources... [  6%] howto/outputting-pdf
reading sources... [  7%] howto/overriding-templates
reading sources... [  7%] howto/static-files/deployment
reading sources... [  7%] howto/static-files/index
reading sources... [  7%] howto/upgrade-version
reading sources... [  7%] howto/windows
reading sources... [  7%] howto/writing-migrations
reading sources... [  8%] index
reading sources... [  8%] internals/contributing/bugs-and-features
reading sources... [  8%] internals/contributing/committing-code
reading sources... [  8%] internals/contributing/index
reading sources... [  8%] internals/contributing/localizing
reading sources... [  8%] internals/contributing/new-contributors
reading sources... [  9%] internals/contributing/triaging-tickets
reading sources... [  9%] internals/contributing/writing-code/coding-style
reading sources... [  9%] internals/contributing/writing-code/index
reading sources... [  9%] internals/contributing/writing-code/javascript
reading sources... [  9%] internals/contributing/writing-code/submitting-patches
reading sources... [  9%] internals/contributing/writing-code/unit-tests
reading sources... [ 10%] internals/contributing/writing-code/working-with-git
reading sources... [ 10%] internals/contributing/writing-documentation
reading sources... [ 10%] internals/deprecation
reading sources... [ 10%] internals/git
reading sources... [ 10%] internals/howto-release-django
reading sources... [ 11%] internals/index
reading sources... [ 11%] internals/mailing-lists
reading sources... [ 11%] internals/organization
reading sources... [ 11%] internals/release-process
reading sources... [ 11%] internals/security
reading sources... [ 11%] intro/contributing
reading sources... [ 12%] intro/index
reading sources... [ 12%] intro/install
reading sources... [ 12%] intro/overview
reading sources... [ 12%] intro/reusable-apps
reading sources... [ 12%] intro/tutorial01
reading sources... [ 12%] intro/tutorial02
reading sources... [ 13%] intro/tutorial03
reading sources... [ 13%] intro/tutorial04
reading sources... [ 13%] intro/tutorial05
reading sources... [ 13%] intro/tutorial06
reading sources... [ 13%] intro/tutorial07
reading sources... [ 13%] intro/tutorial08
reading sources... [ 14%] intro/whatsnext
reading sources... [ 14%] misc/api-stability
reading sources... [ 14%] misc/design-philosophies
reading sources... [ 14%] misc/distributions
reading sources... [ 14%] misc/index
reading sources... [ 14%] ref/applications
reading sources... [ 15%] ref/checks
reading sources... [ 15%] ref/class-based-views/base
reading sources... [ 15%] ref/class-based-views/flattened-index
reading sources... [ 15%] ref/class-based-views/generic-date-based
reading sources... [ 15%] ref/class-based-views/generic-display
reading sources... [ 15%] ref/class-based-views/generic-editing
reading sources... [ 16%] ref/class-based-views/index
reading sources... [ 16%] ref/class-based-views/mixins
reading sources... [ 16%] ref/class-based-views/mixins-date-based
reading sources... [ 16%] ref/class-based-views/mixins-editing
reading sources... [ 16%] ref/class-based-views/mixins-multiple-object
reading sources... [ 16%] ref/class-based-views/mixins-simple
reading sources... [ 17%] ref/class-based-views/mixins-single-object
reading sources... [ 17%] ref/clickjacking
reading sources... [ 17%] ref/contrib/admin/actions
reading sources... [ 17%] ref/contrib/admin/admindocs
reading sources... [ 17%] ref/contrib/admin/filters
reading sources... [ 17%] ref/contrib/admin/index
reading sources... [ 18%] ref/contrib/admin/javascript
reading sources... [ 18%] ref/contrib/auth
reading sources... [ 18%] ref/contrib/contenttypes
reading sources... [ 18%] ref/contrib/flatpages
reading sources... [ 18%] ref/contrib/gis/admin
reading sources... [ 18%] ref/contrib/gis/commands
reading sources... [ 19%] ref/contrib/gis/db-api
reading sources... [ 19%] ref/contrib/gis/deployment
reading sources... [ 19%] ref/contrib/gis/feeds
reading sources... [ 19%] ref/contrib/gis/forms-api
reading sources... [ 19%] ref/contrib/gis/functions
reading sources... [ 19%] ref/contrib/gis/gdal
reading sources... [ 20%] ref/contrib/gis/geoip2
reading sources... [ 20%] ref/contrib/gis/geoquerysets
reading sources... [ 20%] ref/contrib/gis/geos
reading sources... [ 20%] ref/contrib/gis/index
reading sources... [ 20%] ref/contrib/gis/install/geolibs
reading sources... [ 21%] ref/contrib/gis/install/index
reading sources... [ 21%] ref/contrib/gis/install/postgis
reading sources... [ 21%] ref/contrib/gis/install/spatialite
reading sources... [ 21%] ref/contrib/gis/layermapping
reading sources... [ 21%] ref/contrib/gis/measure
reading sources... [ 21%] ref/contrib/gis/model-api
reading sources... [ 22%] ref/contrib/gis/ogrinspect
reading sources... [ 22%] ref/contrib/gis/serializers
reading sources... [ 22%] ref/contrib/gis/sitemaps
reading sources... [ 22%] ref/contrib/gis/testing
reading sources... [ 22%] ref/contrib/gis/tutorial
reading sources... [ 22%] ref/contrib/gis/utils
reading sources... [ 23%] ref/contrib/humanize
reading sources... [ 23%] ref/contrib/index
reading sources... [ 23%] ref/contrib/messages
reading sources... [ 23%] ref/contrib/postgres/aggregates
reading sources... [ 23%] ref/contrib/postgres/constraints
reading sources... [ 23%] ref/contrib/postgres/expressions
reading sources... [ 24%] ref/contrib/postgres/fields
reading sources... [ 24%] ref/contrib/postgres/forms
reading sources... [ 24%] ref/contrib/postgres/functions
reading sources... [ 24%] ref/contrib/postgres/index
reading sources... [ 24%] ref/contrib/postgres/indexes
reading sources... [ 24%] ref/contrib/postgres/lookups
reading sources... [ 25%] ref/contrib/postgres/operations
reading sources... [ 25%] ref/contrib/postgres/search
reading sources... [ 25%] ref/contrib/postgres/validators
reading sources... [ 25%] ref/contrib/redirects
reading sources... [ 25%] ref/contrib/sitemaps
reading sources... [ 25%] ref/contrib/sites
reading sources... [ 26%] ref/contrib/staticfiles
reading sources... [ 26%] ref/contrib/syndication
reading sources... [ 26%] ref/csrf
reading sources... [ 26%] ref/databases
reading sources... [ 26%] ref/django-admin
reading sources... [ 26%] ref/exceptions
reading sources... [ 27%] ref/files/file
reading sources... [ 27%] ref/files/index
reading sources... [ 27%] ref/files/storage
reading sources... [ 27%] ref/files/uploads
reading sources... [ 27%] ref/forms/api
reading sources... [ 27%] ref/forms/fields
reading sources... [ 28%] ref/forms/formsets
reading sources... [ 28%] ref/forms/index
reading sources... [ 28%] ref/forms/models
reading sources... [ 28%] ref/forms/renderers
reading sources... [ 28%] ref/forms/validation
reading sources... [ 28%] ref/forms/widgets
reading sources... [ 29%] ref/index
reading sources... [ 29%] ref/logging
reading sources... [ 29%] ref/middleware
reading sources... [ 29%] ref/migration-operations
reading sources... [ 29%] ref/models/class
reading sources... [ 29%] ref/models/conditional-expressions
reading sources... [ 30%] ref/models/constraints
reading sources... [ 30%] ref/models/database-functions
reading sources... [ 30%] ref/models/expressions
reading sources... [ 30%] ref/models/fields
reading sources... [ 30%] ref/models/index
reading sources... [ 31%] ref/models/indexes
reading sources... [ 31%] ref/models/instances
reading sources... [ 31%] ref/models/lookups
reading sources... [ 31%] ref/models/meta
reading sources... [ 31%] ref/models/options
reading sources... [ 31%] ref/models/querysets
reading sources... [ 32%] ref/models/relations
reading sources... [ 32%] ref/paginator
reading sources... [ 32%] ref/request-response
reading sources... [ 32%] ref/schema-editor
reading sources... [ 32%] ref/settings
reading sources... [ 32%] ref/signals
reading sources... [ 33%] ref/template-response
reading sources... [ 33%] ref/templates/api
reading sources... [ 33%] ref/templates/builtins
reading sources... [ 33%] ref/templates/index
reading sources... [ 33%] ref/templates/language
reading sources... [ 33%] ref/unicode
reading sources... [ 34%] ref/urlresolvers
reading sources... [ 34%] ref/urls
reading sources... [ 34%] ref/utils
reading sources... [ 34%] ref/validators
reading sources... [ 34%] ref/views
reading sources... [ 34%] releases/0.95
reading sources... [ 35%] releases/0.96
reading sources... [ 35%] releases/1.0
reading sources... [ 35%] releases/1.0-porting-guide
reading sources... [ 35%] releases/1.0.1
reading sources... [ 35%] releases/1.0.2
reading sources... [ 35%] releases/1.1
reading sources... [ 36%] releases/1.1.2
reading sources... [ 36%] releases/1.1.3
reading sources... [ 36%] releases/1.1.4
reading sources... [ 36%] releases/1.10
reading sources... [ 36%] releases/1.10.1
reading sources... [ 36%] releases/1.10.2
reading sources... [ 37%] releases/1.10.3
reading sources... [ 37%] releases/1.10.4
reading sources... [ 37%] releases/1.10.5
reading sources... [ 37%] releases/1.10.6
reading sources... [ 37%] releases/1.10.7
reading sources... [ 37%] releases/1.10.8
reading sources... [ 38%] releases/1.11
reading sources... [ 38%] releases/1.11.1
reading sources... [ 38%] releases/1.11.10
reading sources... [ 38%] releases/1.11.11
reading sources... [ 38%] releases/1.11.12
reading sources... [ 38%] releases/1.11.13
reading sources... [ 39%] releases/1.11.14
reading sources... [ 39%] releases/1.11.15
reading sources... [ 39%] releases/1.11.16
reading sources... [ 39%] releases/1.11.17
reading sources... [ 39%] releases/1.11.18
reading sources... [ 39%] releases/1.11.19
reading sources... [ 40%] releases/1.11.2
reading sources... [ 40%] releases/1.11.20
reading sources... [ 40%] releases/1.11.21
reading sources... [ 40%] releases/1.11.22
reading sources... [ 40%] releases/1.11.23
reading sources... [ 41%] releases/1.11.24
reading sources... [ 41%] releases/1.11.25
reading sources... [ 41%] releases/1.11.26
reading sources... [ 41%] releases/1.11.27
reading sources... [ 41%] releases/1.11.28
reading sources... [ 41%] releases/1.11.29
reading sources... [ 42%] releases/1.11.3
reading sources... [ 42%] releases/1.11.4
reading sources... [ 42%] releases/1.11.5
reading sources... [ 42%] releases/1.11.6
reading sources... [ 42%] releases/1.11.7
reading sources... [ 42%] releases/1.11.8
reading sources... [ 43%] releases/1.11.9
reading sources... [ 43%] releases/1.2
reading sources... [ 43%] releases/1.2.1
reading sources... [ 43%] releases/1.2.2
reading sources... [ 43%] releases/1.2.3
reading sources... [ 43%] releases/1.2.4
reading sources... [ 44%] releases/1.2.5
reading sources... [ 44%] releases/1.2.6
reading sources... [ 44%] releases/1.2.7
reading sources... [ 44%] releases/1.3
reading sources... [ 44%] releases/1.3.1
reading sources... [ 44%] releases/1.3.2
reading sources... [ 45%] releases/1.3.3
reading sources... [ 45%] releases/1.3.4
reading sources... [ 45%] releases/1.3.5
reading sources... [ 45%] releases/1.3.6
reading sources... [ 45%] releases/1.3.7
reading sources... [ 45%] releases/1.4
reading sources... [ 46%] releases/1.4.1
reading sources... [ 46%] releases/1.4.10
reading sources... [ 46%] releases/1.4.11
reading sources... [ 46%] releases/1.4.12
reading sources... [ 46%] releases/1.4.13
reading sources... [ 46%] releases/1.4.14
reading sources... [ 47%] releases/1.4.15
reading sources... [ 47%] releases/1.4.16
reading sources... [ 47%] releases/1.4.17
reading sources... [ 47%] releases/1.4.18
reading sources... [ 47%] releases/1.4.19
reading sources... [ 47%] releases/1.4.2
reading sources... [ 48%] releases/1.4.20
reading sources... [ 48%] releases/1.4.21
reading sources... [ 48%] releases/1.4.22
reading sources... [ 48%] releases/1.4.3
reading sources... [ 48%] releases/1.4.4
reading sources... [ 48%] releases/1.4.5
reading sources... [ 49%] releases/1.4.6
reading sources... [ 49%] releases/1.4.7
reading sources... [ 49%] releases/1.4.8
reading sources... [ 49%] releases/1.4.9
reading sources... [ 49%] releases/1.5
reading sources... [ 49%] releases/1.5.1
reading sources... [ 50%] releases/1.5.10
reading sources... [ 50%] releases/1.5.11
reading sources... [ 50%] releases/1.5.12
reading sources... [ 50%] releases/1.5.2
reading sources... [ 50%] releases/1.5.3
reading sources... [ 51%] releases/1.5.4
reading sources... [ 51%] releases/1.5.5
reading sources... [ 51%] releases/1.5.6
reading sources... [ 51%] releases/1.5.7
reading sources... [ 51%] releases/1.5.8
reading sources... [ 51%] releases/1.5.9
reading sources... [ 52%] releases/1.6
reading sources... [ 52%] releases/1.6.1
reading sources... [ 52%] releases/1.6.10
reading sources... [ 52%] releases/1.6.11
reading sources... [ 52%] releases/1.6.2
reading sources... [ 52%] releases/1.6.3
reading sources... [ 53%] releases/1.6.4
reading sources... [ 53%] releases/1.6.5
reading sources... [ 53%] releases/1.6.6
reading sources... [ 53%] releases/1.6.7
reading sources... [ 53%] releases/1.6.8
reading sources... [ 53%] releases/1.6.9
reading sources... [ 54%] releases/1.7
reading sources... [ 54%] releases/1.7.1
reading sources... [ 54%] releases/1.7.10
reading sources... [ 54%] releases/1.7.11
reading sources... [ 54%] releases/1.7.2
reading sources... [ 54%] releases/1.7.3
reading sources... [ 55%] releases/1.7.4
reading sources... [ 55%] releases/1.7.5
reading sources... [ 55%] releases/1.7.6
reading sources... [ 55%] releases/1.7.7
reading sources... [ 55%] releases/1.7.8
reading sources... [ 55%] releases/1.7.9
reading sources... [ 56%] releases/1.8
reading sources... [ 56%] releases/1.8.1
reading sources... [ 56%] releases/1.8.10
reading sources... [ 56%] releases/1.8.11
reading sources... [ 56%] releases/1.8.12
reading sources... [ 56%] releases/1.8.13
reading sources... [ 57%] releases/1.8.14
reading sources... [ 57%] releases/1.8.15
reading sources... [ 57%] releases/1.8.16
reading sources... [ 57%] releases/1.8.17
reading sources... [ 57%] releases/1.8.18
reading sources... [ 57%] releases/1.8.19
reading sources... [ 58%] releases/1.8.2
reading sources... [ 58%] releases/1.8.3
reading sources... [ 58%] releases/1.8.4
reading sources... [ 58%] releases/1.8.5
reading sources... [ 58%] releases/1.8.6
reading sources... [ 58%] releases/1.8.7
reading sources... [ 59%] releases/1.8.8
reading sources... [ 59%] releases/1.8.9
reading sources... [ 59%] releases/1.9
reading sources... [ 59%] releases/1.9.1
reading sources... [ 59%] releases/1.9.10
reading sources... [ 59%] releases/1.9.11
reading sources... [ 60%] releases/1.9.12
reading sources... [ 60%] releases/1.9.13
reading sources... [ 60%] releases/1.9.2
reading sources... [ 60%] releases/1.9.3
reading sources... [ 60%] releases/1.9.4
reading sources... [ 61%] releases/1.9.5
reading sources... [ 61%] releases/1.9.6
reading sources... [ 61%] releases/1.9.7
reading sources... [ 61%] releases/1.9.8
reading sources... [ 61%] releases/1.9.9
reading sources... [ 61%] releases/2.0
reading sources... [ 62%] releases/2.0.1
reading sources... [ 62%] releases/2.0.10
reading sources... [ 62%] releases/2.0.11
reading sources... [ 62%] releases/2.0.12
reading sources... [ 62%] releases/2.0.13
reading sources... [ 62%] releases/2.0.2
reading sources... [ 63%] releases/2.0.3
reading sources... [ 63%] releases/2.0.4
reading sources... [ 63%] releases/2.0.5
reading sources... [ 63%] releases/2.0.6
reading sources... [ 63%] releases/2.0.7
reading sources... [ 63%] releases/2.0.8
reading sources... [ 64%] releases/2.0.9
reading sources... [ 64%] releases/2.1
reading sources... [ 64%] releases/2.1.1
reading sources... [ 64%] releases/2.1.10
reading sources... [ 64%] releases/2.1.11
reading sources... [ 64%] releases/2.1.12
reading sources... [ 65%] releases/2.1.13
reading sources... [ 65%] releases/2.1.14
reading sources... [ 65%] releases/2.1.15
reading sources... [ 65%] releases/2.1.2
reading sources... [ 65%] releases/2.1.3
reading sources... [ 65%] releases/2.1.4
reading sources... [ 66%] releases/2.1.5
reading sources... [ 66%] releases/2.1.6
reading sources... [ 66%] releases/2.1.7
reading sources... [ 66%] releases/2.1.8
reading sources... [ 66%] releases/2.1.9
reading sources... [ 66%] releases/2.2
reading sources... [ 67%] releases/2.2.1
reading sources... [ 67%] releases/2.2.10
reading sources... [ 67%] releases/2.2.11
reading sources... [ 67%] releases/2.2.12
reading sources... [ 67%] releases/2.2.13
reading sources... [ 67%] releases/2.2.14
reading sources... [ 68%] releases/2.2.15
reading sources... [ 68%] releases/2.2.16
reading sources... [ 68%] releases/2.2.17
reading sources... [ 68%] releases/2.2.18
reading sources... [ 68%] releases/2.2.19
reading sources... [ 68%] releases/2.2.2
reading sources... [ 69%] releases/2.2.20
reading sources... [ 69%] releases/2.2.21
reading sources... [ 69%] releases/2.2.22
reading sources... [ 69%] releases/2.2.23
reading sources... [ 69%] releases/2.2.24
reading sources... [ 69%] releases/2.2.25
reading sources... [ 70%] releases/2.2.26
reading sources... [ 70%] releases/2.2.27
reading sources... [ 70%] releases/2.2.28
reading sources... [ 70%] releases/2.2.3
reading sources... [ 70%] releases/2.2.4
reading sources... [ 71%] releases/2.2.5
reading sources... [ 71%] releases/2.2.6
reading sources... [ 71%] releases/2.2.7
reading sources... [ 71%] releases/2.2.8
reading sources... [ 71%] releases/2.2.9
reading sources... [ 71%] releases/3.0
reading sources... [ 72%] releases/3.0.1
reading sources... [ 72%] releases/3.0.10
reading sources... [ 72%] releases/3.0.11
reading sources... [ 72%] releases/3.0.12
reading sources... [ 72%] releases/3.0.13
reading sources... [ 72%] releases/3.0.14
reading sources... [ 73%] releases/3.0.2
reading sources... [ 73%] releases/3.0.3
reading sources... [ 73%] releases/3.0.4
reading sources... [ 73%] releases/3.0.5
reading sources... [ 73%] releases/3.0.6
reading sources... [ 73%] releases/3.0.7
reading sources... [ 74%] releases/3.0.8
reading sources... [ 74%] releases/3.0.9
reading sources... [ 74%] releases/3.1
reading sources... [ 74%] releases/3.1.1
reading sources... [ 74%] releases/3.1.10
reading sources... [ 74%] releases/3.1.11
reading sources... [ 75%] releases/3.1.12
reading sources... [ 75%] releases/3.1.13
reading sources... [ 75%] releases/3.1.14
reading sources... [ 75%] releases/3.1.2
reading sources... [ 75%] releases/3.1.3
reading sources... [ 75%] releases/3.1.4
reading sources... [ 76%] releases/3.1.5
reading sources... [ 76%] releases/3.1.6
reading sources... [ 76%] releases/3.1.7
reading sources... [ 76%] releases/3.1.8
reading sources... [ 76%] releases/3.1.9
reading sources... [ 76%] releases/3.2
reading sources... [ 77%] releases/3.2.1
reading sources... [ 77%] releases/3.2.10
reading sources... [ 77%] releases/3.2.11
reading sources... [ 77%] releases/3.2.12
reading sources... [ 77%] releases/3.2.13
reading sources... [ 77%] releases/3.2.14
reading sources... [ 78%] releases/3.2.15
reading sources... [ 78%] releases/3.2.16
reading sources... [ 78%] releases/3.2.17
reading sources... [ 78%] releases/3.2.18
reading sources... [ 78%] releases/3.2.19
reading sources... [ 78%] releases/3.2.2
reading sources... [ 79%] releases/3.2.20
reading sources... [ 79%] releases/3.2.21
reading sources... [ 79%] releases/3.2.22
reading sources... [ 79%] releases/3.2.23
reading sources... [ 79%] releases/3.2.24
reading sources... [ 79%] releases/3.2.25
reading sources... [ 80%] releases/3.2.3
reading sources... [ 80%] releases/3.2.4
reading sources... [ 80%] releases/3.2.5
reading sources... [ 80%] releases/3.2.6
reading sources... [ 80%] releases/3.2.7
reading sources... [ 81%] releases/3.2.8
reading sources... [ 81%] releases/3.2.9
reading sources... [ 81%] releases/4.0
reading sources... [ 81%] releases/4.0.1
reading sources... [ 81%] releases/4.0.10
reading sources... [ 81%] releases/4.0.2
reading sources... [ 82%] releases/4.0.3
reading sources... [ 82%] releases/4.0.4
reading sources... [ 82%] releases/4.0.5
reading sources... [ 82%] releases/4.0.6
reading sources... [ 82%] releases/4.0.7
reading sources... [ 82%] releases/4.0.8
reading sources... [ 83%] releases/4.0.9
reading sources... [ 83%] releases/4.1
reading sources... [ 83%] releases/4.1.1
reading sources... [ 83%] releases/4.1.10
reading sources... [ 83%] releases/4.1.11
reading sources... [ 83%] releases/4.1.12
reading sources... [ 84%] releases/4.1.13
reading sources... [ 84%] releases/4.1.2
reading sources... [ 84%] releases/4.1.3
reading sources... [ 84%] releases/4.1.4
reading sources... [ 84%] releases/4.1.5
reading sources... [ 84%] releases/4.1.6
reading sources... [ 85%] releases/4.1.7
reading sources... [ 85%] releases/4.1.8
reading sources... [ 85%] releases/4.1.9
reading sources... [ 85%] releases/4.2
reading sources... [ 85%] releases/4.2.1
reading sources... [ 85%] releases/4.2.10
reading sources... [ 86%] releases/4.2.11
reading sources... [ 86%] releases/4.2.12
reading sources... [ 86%] releases/4.2.13
reading sources... [ 86%] releases/4.2.14
reading sources... [ 86%] releases/4.2.15
reading sources... [ 86%] releases/4.2.16
reading sources... [ 87%] releases/4.2.17
reading sources... [ 87%] releases/4.2.18
reading sources... [ 87%] releases/4.2.19
reading sources... [ 87%] releases/4.2.2
reading sources... [ 87%] releases/4.2.20
reading sources... [ 87%] releases/4.2.3
reading sources... [ 88%] releases/4.2.4
reading sources... [ 88%] releases/4.2.5
reading sources... [ 88%] releases/4.2.6
reading sources... [ 88%] releases/4.2.7
reading sources... [ 88%] releases/4.2.8
reading sources... [ 88%] releases/4.2.9
reading sources... [ 89%] releases/index
reading sources... [ 89%] releases/security
reading sources... [ 89%] topics/async
reading sources... [ 89%] topics/auth/customizing
reading sources... [ 89%] topics/auth/default
reading sources... [ 89%] topics/auth/index
reading sources... [ 90%] topics/auth/passwords
reading sources... [ 90%] topics/cache
reading sources... [ 90%] topics/checks
reading sources... [ 90%] topics/class-based-views/generic-display
reading sources... [ 90%] topics/class-based-views/generic-editing
reading sources... [ 91%] topics/class-based-views/index
reading sources... [ 91%] topics/class-based-views/intro
reading sources... [ 91%] topics/class-based-views/mixins
reading sources... [ 91%] topics/conditional-view-processing
reading sources... [ 91%] topics/db/aggregation
reading sources... [ 91%] topics/db/examples/index
reading sources... [ 92%] topics/db/examples/many_to_many
reading sources... [ 92%] topics/db/examples/many_to_one
reading sources... [ 92%] topics/db/examples/one_to_one
reading sources... [ 92%] topics/db/fixtures
reading sources... [ 92%] topics/db/index
reading sources... [ 92%] topics/db/instrumentation
reading sources... [ 93%] topics/db/managers
reading sources... [ 93%] topics/db/models
reading sources... [ 93%] topics/db/multi-db
reading sources... [ 93%] topics/db/optimization
reading sources... [ 93%] topics/db/queries
reading sources... [ 93%] topics/db/search
reading sources... [ 94%] topics/db/sql
reading sources... [ 94%] topics/db/tablespaces
reading sources... [ 94%] topics/db/transactions
reading sources... [ 94%] topics/email
reading sources... [ 94%] topics/external-packages
reading sources... [ 94%] topics/files
reading sources... [ 95%] topics/forms/formsets
reading sources... [ 95%] topics/forms/index
reading sources... [ 95%] topics/forms/media
reading sources... [ 95%] topics/forms/modelforms
reading sources... [ 95%] topics/http/decorators
reading sources... [ 95%] topics/http/file-uploads
reading sources... [ 96%] topics/http/generic-views
reading sources... [ 96%] topics/http/index
reading sources... [ 96%] topics/http/middleware
reading sources... [ 96%] topics/http/sessions
reading sources... [ 96%] topics/http/shortcuts
reading sources... [ 96%] topics/http/urls
reading sources... [ 97%] topics/http/views
reading sources... [ 97%] topics/i18n/formatting
reading sources... [ 97%] topics/i18n/index
reading sources... [ 97%] topics/i18n/timezones
reading sources... [ 97%] topics/i18n/translation
reading sources... [ 97%] topics/index
reading sources... [ 98%] topics/install
reading sources... [ 98%] topics/logging
reading sources... [ 98%] topics/migrations
reading sources... [ 98%] topics/pagination
reading sources... [ 98%] topics/performance
reading sources... [ 98%] topics/security
reading sources... [ 99%] topics/serialization
reading sources... [ 99%] topics/settings
reading sources... [ 99%] topics/signals
reading sources... [ 99%] topics/signing
reading sources... [ 99%] topics/templates
reading sources... [ 99%] topics/testing/advanced
reading sources... [100%] topics/testing/index
reading sources... [100%] topics/testing/overview
reading sources... [100%] topics/testing/tools

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
copying assets... 
copying static files... 
Writing evaluated template result to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/_build/html/_static/basic.css
Writing evaluated template result to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/_build/html/_static/documentation_options.js
Writing evaluated template result to /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/_build/html/_static/language_data.js
copying static files: done
copying extra files... 
copying extra files: done
copying assets: done
writing output... [  0%] contents
writing output... [  0%] faq/admin
writing output... [  1%] faq/contributing
writing output... [  1%] faq/general
writing output... [  1%] faq/help
writing output... [  1%] faq/index
writing output... [  1%] faq/install
writing output... [  1%] faq/models
writing output... [  2%] faq/troubleshooting
writing output... [  2%] faq/usage
writing output... [  2%] glossary
writing output... [  2%] howto/auth-remote-user
writing output... [  2%] howto/csrf
writing output... [  2%] howto/custom-file-storage
writing output... [  3%] howto/custom-lookups
writing output... [  3%] howto/custom-management-commands
writing output... [  3%] howto/custom-model-fields
writing output... [  3%] howto/custom-template-backend
writing output... [  3%] howto/custom-template-tags
writing output... [  3%] howto/delete-app
writing output... [  4%] howto/deployment/asgi/daphne
writing output... [  4%] howto/deployment/asgi/hypercorn
writing output... [  4%] howto/deployment/asgi/index
writing output... [  4%] howto/deployment/asgi/uvicorn
writing output... [  4%] howto/deployment/checklist
writing output... [  4%] howto/deployment/index
writing output... [  5%] howto/deployment/wsgi/apache-auth
writing output... [  5%] howto/deployment/wsgi/gunicorn
writing output... [  5%] howto/deployment/wsgi/index
writing output... [  5%] howto/deployment/wsgi/modwsgi
writing output... [  5%] howto/deployment/wsgi/uwsgi
writing output... [  5%] howto/error-reporting
writing output... [  6%] howto/index
writing output... [  6%] howto/initial-data
writing output... [  6%] howto/legacy-databases
writing output... [  6%] howto/logging
writing output... [  6%] howto/outputting-csv
writing output... [  6%] howto/outputting-pdf
writing output... [  7%] howto/overriding-templates
writing output... [  7%] howto/static-files/deployment
writing output... [  7%] howto/static-files/index
writing output... [  7%] howto/upgrade-version
writing output... [  7%] howto/windows
writing output... [  7%] howto/writing-migrations
writing output... [  8%] index
writing output... [  8%] internals/contributing/bugs-and-features
writing output... [  8%] internals/contributing/committing-code
writing output... [  8%] internals/contributing/index
writing output... [  8%] internals/contributing/localizing
writing output... [  8%] internals/contributing/new-contributors
writing output... [  9%] internals/contributing/triaging-tickets
writing output... [  9%] internals/contributing/writing-code/coding-style
writing output... [  9%] internals/contributing/writing-code/index
writing output... [  9%] internals/contributing/writing-code/javascript
writing output... [  9%] internals/contributing/writing-code/submitting-patches
writing output... [  9%] internals/contributing/writing-code/unit-tests
writing output... [ 10%] internals/contributing/writing-code/working-with-git
writing output... [ 10%] internals/contributing/writing-documentation
writing output... [ 10%] internals/deprecation
writing output... [ 10%] internals/git
writing output... [ 10%] internals/howto-release-django
writing output... [ 11%] internals/index
writing output... [ 11%] internals/mailing-lists
writing output... [ 11%] internals/organization
writing output... [ 11%] internals/release-process
writing output... [ 11%] internals/security
writing output... [ 11%] intro/contributing
writing output... [ 12%] intro/index
writing output... [ 12%] intro/install
writing output... [ 12%] intro/overview
writing output... [ 12%] intro/reusable-apps
writing output... [ 12%] intro/tutorial01
writing output... [ 12%] intro/tutorial02
writing output... [ 13%] intro/tutorial03
writing output... [ 13%] intro/tutorial04
writing output... [ 13%] intro/tutorial05
writing output... [ 13%] intro/tutorial06
writing output... [ 13%] intro/tutorial07
writing output... [ 13%] intro/tutorial08
writing output... [ 14%] intro/whatsnext
writing output... [ 14%] misc/api-stability
writing output... [ 14%] misc/design-philosophies
writing output... [ 14%] misc/distributions
writing output... [ 14%] misc/index
writing output... [ 14%] ref/applications
writing output... [ 15%] ref/checks
writing output... [ 15%] ref/class-based-views/base
writing output... [ 15%] ref/class-based-views/flattened-index
writing output... [ 15%] ref/class-based-views/generic-date-based
writing output... [ 15%] ref/class-based-views/generic-display
writing output... [ 15%] ref/class-based-views/generic-editing
writing output... [ 16%] ref/class-based-views/index
writing output... [ 16%] ref/class-based-views/mixins
writing output... [ 16%] ref/class-based-views/mixins-date-based
writing output... [ 16%] ref/class-based-views/mixins-editing
writing output... [ 16%] ref/class-based-views/mixins-multiple-object
writing output... [ 16%] ref/class-based-views/mixins-simple
writing output... [ 17%] ref/class-based-views/mixins-single-object
writing output... [ 17%] ref/clickjacking
writing output... [ 17%] ref/contrib/admin/actions
writing output... [ 17%] ref/contrib/admin/admindocs
writing output... [ 17%] ref/contrib/admin/filters
writing output... [ 17%] ref/contrib/admin/index
writing output... [ 18%] ref/contrib/admin/javascript
writing output... [ 18%] ref/contrib/auth
writing output... [ 18%] ref/contrib/contenttypes
writing output... [ 18%] ref/contrib/flatpages
writing output... [ 18%] ref/contrib/gis/admin
writing output... [ 18%] ref/contrib/gis/commands
writing output... [ 19%] ref/contrib/gis/db-api
writing output... [ 19%] ref/contrib/gis/deployment
writing output... [ 19%] ref/contrib/gis/feeds
writing output... [ 19%] ref/contrib/gis/forms-api
writing output... [ 19%] ref/contrib/gis/functions
writing output... [ 19%] ref/contrib/gis/gdal
writing output... [ 20%] ref/contrib/gis/geoip2
writing output... [ 20%] ref/contrib/gis/geoquerysets
writing output... [ 20%] ref/contrib/gis/geos
writing output... [ 20%] ref/contrib/gis/index
writing output... [ 20%] ref/contrib/gis/install/geolibs
writing output... [ 21%] ref/contrib/gis/install/index
writing output... [ 21%] ref/contrib/gis/install/postgis
writing output... [ 21%] ref/contrib/gis/install/spatialite
writing output... [ 21%] ref/contrib/gis/layermapping
writing output... [ 21%] ref/contrib/gis/measure
writing output... [ 21%] ref/contrib/gis/model-api
writing output... [ 22%] ref/contrib/gis/ogrinspect
writing output... [ 22%] ref/contrib/gis/serializers
writing output... [ 22%] ref/contrib/gis/sitemaps
writing output... [ 22%] ref/contrib/gis/testing
writing output... [ 22%] ref/contrib/gis/tutorial
writing output... [ 22%] ref/contrib/gis/utils
writing output... [ 23%] ref/contrib/humanize
writing output... [ 23%] ref/contrib/index
writing output... [ 23%] ref/contrib/messages
writing output... [ 23%] ref/contrib/postgres/aggregates
writing output... [ 23%] ref/contrib/postgres/constraints
writing output... [ 23%] ref/contrib/postgres/expressions
writing output... [ 24%] ref/contrib/postgres/fields
writing output... [ 24%] ref/contrib/postgres/forms
writing output... [ 24%] ref/contrib/postgres/functions
writing output... [ 24%] ref/contrib/postgres/index
writing output... [ 24%] ref/contrib/postgres/indexes
writing output... [ 24%] ref/contrib/postgres/lookups
writing output... [ 25%] ref/contrib/postgres/operations
writing output... [ 25%] ref/contrib/postgres/search
writing output... [ 25%] ref/contrib/postgres/validators
writing output... [ 25%] ref/contrib/redirects
writing output... [ 25%] ref/contrib/sitemaps
writing output... [ 25%] ref/contrib/sites
writing output... [ 26%] ref/contrib/staticfiles
writing output... [ 26%] ref/contrib/syndication
writing output... [ 26%] ref/csrf
writing output... [ 26%] ref/databases
writing output... [ 26%] ref/django-admin
writing output... [ 26%] ref/exceptions
writing output... [ 27%] ref/files/file
writing output... [ 27%] ref/files/index
writing output... [ 27%] ref/files/storage
writing output... [ 27%] ref/files/uploads
writing output... [ 27%] ref/forms/api
writing output... [ 27%] ref/forms/fields
writing output... [ 28%] ref/forms/formsets
writing output... [ 28%] ref/forms/index
writing output... [ 28%] ref/forms/models
writing output... [ 28%] ref/forms/renderers
writing output... [ 28%] ref/forms/validation
writing output... [ 28%] ref/forms/widgets
writing output... [ 29%] ref/index
writing output... [ 29%] ref/logging
writing output... [ 29%] ref/middleware
writing output... [ 29%] ref/migration-operations
writing output... [ 29%] ref/models/class
writing output... [ 29%] ref/models/conditional-expressions
writing output... [ 30%] ref/models/constraints
writing output... [ 30%] ref/models/database-functions
writing output... [ 30%] ref/models/expressions
writing output... [ 30%] ref/models/fields
writing output... [ 30%] ref/models/index
writing output... [ 31%] ref/models/indexes
writing output... [ 31%] ref/models/instances
writing output... [ 31%] ref/models/lookups
writing output... [ 31%] ref/models/meta
writing output... [ 31%] ref/models/options
writing output... [ 31%] ref/models/querysets
writing output... [ 32%] ref/models/relations
writing output... [ 32%] ref/paginator
writing output... [ 32%] ref/request-response
writing output... [ 32%] ref/schema-editor
writing output... [ 32%] ref/settings
writing output... [ 32%] ref/signals
writing output... [ 33%] ref/template-response
writing output... [ 33%] ref/templates/api
writing output... [ 33%] ref/templates/builtins
writing output... [ 33%] ref/templates/index
writing output... [ 33%] ref/templates/language
writing output... [ 33%] ref/unicode
writing output... [ 34%] ref/urlresolvers
writing output... [ 34%] ref/urls
writing output... [ 34%] ref/utils
writing output... [ 34%] ref/validators
writing output... [ 34%] ref/views
writing output... [ 34%] releases/0.95
writing output... [ 35%] releases/0.96
writing output... [ 35%] releases/1.0
writing output... [ 35%] releases/1.0-porting-guide
writing output... [ 35%] releases/1.0.1
writing output... [ 35%] releases/1.0.2
writing output... [ 35%] releases/1.1
writing output... [ 36%] releases/1.1.2
writing output... [ 36%] releases/1.1.3
writing output... [ 36%] releases/1.1.4
writing output... [ 36%] releases/1.10
writing output... [ 36%] releases/1.10.1
writing output... [ 36%] releases/1.10.2
writing output... [ 37%] releases/1.10.3
writing output... [ 37%] releases/1.10.4
writing output... [ 37%] releases/1.10.5
writing output... [ 37%] releases/1.10.6
writing output... [ 37%] releases/1.10.7
writing output... [ 37%] releases/1.10.8
writing output... [ 38%] releases/1.11
writing output... [ 38%] releases/1.11.1
writing output... [ 38%] releases/1.11.10
writing output... [ 38%] releases/1.11.11
writing output... [ 38%] releases/1.11.12
writing output... [ 38%] releases/1.11.13
writing output... [ 39%] releases/1.11.14
writing output... [ 39%] releases/1.11.15
writing output... [ 39%] releases/1.11.16
writing output... [ 39%] releases/1.11.17
writing output... [ 39%] releases/1.11.18
writing output... [ 39%] releases/1.11.19
writing output... [ 40%] releases/1.11.2
writing output... [ 40%] releases/1.11.20
writing output... [ 40%] releases/1.11.21
writing output... [ 40%] releases/1.11.22
writing output... [ 40%] releases/1.11.23
writing output... [ 41%] releases/1.11.24
writing output... [ 41%] releases/1.11.25
writing output... [ 41%] releases/1.11.26
writing output... [ 41%] releases/1.11.27
writing output... [ 41%] releases/1.11.28
writing output... [ 41%] releases/1.11.29
writing output... [ 42%] releases/1.11.3
writing output... [ 42%] releases/1.11.4
writing output... [ 42%] releases/1.11.5
writing output... [ 42%] releases/1.11.6
writing output... [ 42%] releases/1.11.7
writing output... [ 42%] releases/1.11.8
writing output... [ 43%] releases/1.11.9
writing output... [ 43%] releases/1.2
writing output... [ 43%] releases/1.2.1
writing output... [ 43%] releases/1.2.2
writing output... [ 43%] releases/1.2.3
writing output... [ 43%] releases/1.2.4
writing output... [ 44%] releases/1.2.5
writing output... [ 44%] releases/1.2.6
writing output... [ 44%] releases/1.2.7
writing output... [ 44%] releases/1.3
writing output... [ 44%] releases/1.3.1
writing output... [ 44%] releases/1.3.2
writing output... [ 45%] releases/1.3.3
writing output... [ 45%] releases/1.3.4
writing output... [ 45%] releases/1.3.5
writing output... [ 45%] releases/1.3.6
writing output... [ 45%] releases/1.3.7
writing output... [ 45%] releases/1.4
writing output... [ 46%] releases/1.4.1
writing output... [ 46%] releases/1.4.10
writing output... [ 46%] releases/1.4.11
writing output... [ 46%] releases/1.4.12
writing output... [ 46%] releases/1.4.13
writing output... [ 46%] releases/1.4.14
writing output... [ 47%] releases/1.4.15
writing output... [ 47%] releases/1.4.16
writing output... [ 47%] releases/1.4.17
writing output... [ 47%] releases/1.4.18
writing output... [ 47%] releases/1.4.19
writing output... [ 47%] releases/1.4.2
writing output... [ 48%] releases/1.4.20
writing output... [ 48%] releases/1.4.21
writing output... [ 48%] releases/1.4.22
writing output... [ 48%] releases/1.4.3
writing output... [ 48%] releases/1.4.4
writing output... [ 48%] releases/1.4.5
writing output... [ 49%] releases/1.4.6
writing output... [ 49%] releases/1.4.7
writing output... [ 49%] releases/1.4.8
writing output... [ 49%] releases/1.4.9
writing output... [ 49%] releases/1.5
writing output... [ 49%] releases/1.5.1
writing output... [ 50%] releases/1.5.10
writing output... [ 50%] releases/1.5.11
writing output... [ 50%] releases/1.5.12
writing output... [ 50%] releases/1.5.2
writing output... [ 50%] releases/1.5.3
writing output... [ 51%] releases/1.5.4
writing output... [ 51%] releases/1.5.5
writing output... [ 51%] releases/1.5.6
writing output... [ 51%] releases/1.5.7
writing output... [ 51%] releases/1.5.8
writing output... [ 51%] releases/1.5.9
writing output... [ 52%] releases/1.6
writing output... [ 52%] releases/1.6.1
writing output... [ 52%] releases/1.6.10
writing output... [ 52%] releases/1.6.11
writing output... [ 52%] releases/1.6.2
writing output... [ 52%] releases/1.6.3
writing output... [ 53%] releases/1.6.4
writing output... [ 53%] releases/1.6.5
writing output... [ 53%] releases/1.6.6
writing output... [ 53%] releases/1.6.7
writing output... [ 53%] releases/1.6.8
writing output... [ 53%] releases/1.6.9
writing output... [ 54%] releases/1.7
writing output... [ 54%] releases/1.7.1
writing output... [ 54%] releases/1.7.10
writing output... [ 54%] releases/1.7.11
writing output... [ 54%] releases/1.7.2
writing output... [ 54%] releases/1.7.3
writing output... [ 55%] releases/1.7.4
writing output... [ 55%] releases/1.7.5
writing output... [ 55%] releases/1.7.6
writing output... [ 55%] releases/1.7.7
writing output... [ 55%] releases/1.7.8
writing output... [ 55%] releases/1.7.9
writing output... [ 56%] releases/1.8
writing output... [ 56%] releases/1.8.1
writing output... [ 56%] releases/1.8.10
writing output... [ 56%] releases/1.8.11
writing output... [ 56%] releases/1.8.12
writing output... [ 56%] releases/1.8.13
writing output... [ 57%] releases/1.8.14
writing output... [ 57%] releases/1.8.15
writing output... [ 57%] releases/1.8.16
writing output... [ 57%] releases/1.8.17
writing output... [ 57%] releases/1.8.18
writing output... [ 57%] releases/1.8.19
writing output... [ 58%] releases/1.8.2
writing output... [ 58%] releases/1.8.3
writing output... [ 58%] releases/1.8.4
writing output... [ 58%] releases/1.8.5
writing output... [ 58%] releases/1.8.6
writing output... [ 58%] releases/1.8.7
writing output... [ 59%] releases/1.8.8
writing output... [ 59%] releases/1.8.9
writing output... [ 59%] releases/1.9
writing output... [ 59%] releases/1.9.1
writing output... [ 59%] releases/1.9.10
writing output... [ 59%] releases/1.9.11
writing output... [ 60%] releases/1.9.12
writing output... [ 60%] releases/1.9.13
writing output... [ 60%] releases/1.9.2
writing output... [ 60%] releases/1.9.3
writing output... [ 60%] releases/1.9.4
writing output... [ 61%] releases/1.9.5
writing output... [ 61%] releases/1.9.6
writing output... [ 61%] releases/1.9.7
writing output... [ 61%] releases/1.9.8
writing output... [ 61%] releases/1.9.9
writing output... [ 61%] releases/2.0
writing output... [ 62%] releases/2.0.1
writing output... [ 62%] releases/2.0.10
writing output... [ 62%] releases/2.0.11
writing output... [ 62%] releases/2.0.12
writing output... [ 62%] releases/2.0.13
writing output... [ 62%] releases/2.0.2
writing output... [ 63%] releases/2.0.3
writing output... [ 63%] releases/2.0.4
writing output... [ 63%] releases/2.0.5
writing output... [ 63%] releases/2.0.6
writing output... [ 63%] releases/2.0.7
writing output... [ 63%] releases/2.0.8
writing output... [ 64%] releases/2.0.9
writing output... [ 64%] releases/2.1
writing output... [ 64%] releases/2.1.1
writing output... [ 64%] releases/2.1.10
writing output... [ 64%] releases/2.1.11
writing output... [ 64%] releases/2.1.12
writing output... [ 65%] releases/2.1.13
writing output... [ 65%] releases/2.1.14
writing output... [ 65%] releases/2.1.15
writing output... [ 65%] releases/2.1.2
writing output... [ 65%] releases/2.1.3
writing output... [ 65%] releases/2.1.4
writing output... [ 66%] releases/2.1.5
writing output... [ 66%] releases/2.1.6
writing output... [ 66%] releases/2.1.7
writing output... [ 66%] releases/2.1.8
writing output... [ 66%] releases/2.1.9
writing output... [ 66%] releases/2.2
writing output... [ 67%] releases/2.2.1
writing output... [ 67%] releases/2.2.10
writing output... [ 67%] releases/2.2.11
writing output... [ 67%] releases/2.2.12
writing output... [ 67%] releases/2.2.13
writing output... [ 67%] releases/2.2.14
writing output... [ 68%] releases/2.2.15
writing output... [ 68%] releases/2.2.16
writing output... [ 68%] releases/2.2.17
writing output... [ 68%] releases/2.2.18
writing output... [ 68%] releases/2.2.19
writing output... [ 68%] releases/2.2.2
writing output... [ 69%] releases/2.2.20
writing output... [ 69%] releases/2.2.21
writing output... [ 69%] releases/2.2.22
writing output... [ 69%] releases/2.2.23
writing output... [ 69%] releases/2.2.24
writing output... [ 69%] releases/2.2.25
writing output... [ 70%] releases/2.2.26
writing output... [ 70%] releases/2.2.27
writing output... [ 70%] releases/2.2.28
writing output... [ 70%] releases/2.2.3
writing output... [ 70%] releases/2.2.4
writing output... [ 71%] releases/2.2.5
writing output... [ 71%] releases/2.2.6
writing output... [ 71%] releases/2.2.7
writing output... [ 71%] releases/2.2.8
writing output... [ 71%] releases/2.2.9
writing output... [ 71%] releases/3.0
writing output... [ 72%] releases/3.0.1
writing output... [ 72%] releases/3.0.10
writing output... [ 72%] releases/3.0.11
writing output... [ 72%] releases/3.0.12
writing output... [ 72%] releases/3.0.13
writing output... [ 72%] releases/3.0.14
writing output... [ 73%] releases/3.0.2
writing output... [ 73%] releases/3.0.3
writing output... [ 73%] releases/3.0.4
writing output... [ 73%] releases/3.0.5
writing output... [ 73%] releases/3.0.6
writing output... [ 73%] releases/3.0.7
writing output... [ 74%] releases/3.0.8
writing output... [ 74%] releases/3.0.9
writing output... [ 74%] releases/3.1
writing output... [ 74%] releases/3.1.1
writing output... [ 74%] releases/3.1.10
writing output... [ 74%] releases/3.1.11
writing output... [ 75%] releases/3.1.12
writing output... [ 75%] releases/3.1.13
writing output... [ 75%] releases/3.1.14
writing output... [ 75%] releases/3.1.2
writing output... [ 75%] releases/3.1.3
writing output... [ 75%] releases/3.1.4
writing output... [ 76%] releases/3.1.5
writing output... [ 76%] releases/3.1.6
writing output... [ 76%] releases/3.1.7
writing output... [ 76%] releases/3.1.8
writing output... [ 76%] releases/3.1.9
writing output... [ 76%] releases/3.2
writing output... [ 77%] releases/3.2.1
writing output... [ 77%] releases/3.2.10
writing output... [ 77%] releases/3.2.11
writing output... [ 77%] releases/3.2.12
writing output... [ 77%] releases/3.2.13
writing output... [ 77%] releases/3.2.14
writing output... [ 78%] releases/3.2.15
writing output... [ 78%] releases/3.2.16
writing output... [ 78%] releases/3.2.17
writing output... [ 78%] releases/3.2.18
writing output... [ 78%] releases/3.2.19
writing output... [ 78%] releases/3.2.2
writing output... [ 79%] releases/3.2.20
writing output... [ 79%] releases/3.2.21
writing output... [ 79%] releases/3.2.22
writing output... [ 79%] releases/3.2.23
writing output... [ 79%] releases/3.2.24
writing output... [ 79%] releases/3.2.25
writing output... [ 80%] releases/3.2.3
writing output... [ 80%] releases/3.2.4
writing output... [ 80%] releases/3.2.5
writing output... [ 80%] releases/3.2.6
writing output... [ 80%] releases/3.2.7
writing output... [ 81%] releases/3.2.8
writing output... [ 81%] releases/3.2.9
writing output... [ 81%] releases/4.0
writing output... [ 81%] releases/4.0.1
writing output... [ 81%] releases/4.0.10
writing output... [ 81%] releases/4.0.2
writing output... [ 82%] releases/4.0.3
writing output... [ 82%] releases/4.0.4
writing output... [ 82%] releases/4.0.5
writing output... [ 82%] releases/4.0.6
writing output... [ 82%] releases/4.0.7
writing output... [ 82%] releases/4.0.8
writing output... [ 83%] releases/4.0.9
writing output... [ 83%] releases/4.1
writing output... [ 83%] releases/4.1.1
writing output... [ 83%] releases/4.1.10
writing output... [ 83%] releases/4.1.11
writing output... [ 83%] releases/4.1.12
writing output... [ 84%] releases/4.1.13
writing output... [ 84%] releases/4.1.2
writing output... [ 84%] releases/4.1.3
writing output... [ 84%] releases/4.1.4
writing output... [ 84%] releases/4.1.5
writing output... [ 84%] releases/4.1.6
writing output... [ 85%] releases/4.1.7
writing output... [ 85%] releases/4.1.8
writing output... [ 85%] releases/4.1.9
writing output... [ 85%] releases/4.2
writing output... [ 85%] releases/4.2.1
writing output... [ 85%] releases/4.2.10
writing output... [ 86%] releases/4.2.11
writing output... [ 86%] releases/4.2.12
writing output... [ 86%] releases/4.2.13
writing output... [ 86%] releases/4.2.14
writing output... [ 86%] releases/4.2.15
writing output... [ 86%] releases/4.2.16
writing output... [ 87%] releases/4.2.17
writing output... [ 87%] releases/4.2.18
writing output... [ 87%] releases/4.2.19
writing output... [ 87%] releases/4.2.2
writing output... [ 87%] releases/4.2.20
writing output... [ 87%] releases/4.2.3
writing output... [ 88%] releases/4.2.4
writing output... [ 88%] releases/4.2.5
writing output... [ 88%] releases/4.2.6
writing output... [ 88%] releases/4.2.7
writing output... [ 88%] releases/4.2.8
writing output... [ 88%] releases/4.2.9
writing output... [ 89%] releases/index
writing output... [ 89%] releases/security
writing output... [ 89%] topics/async
writing output... [ 89%] topics/auth/customizing
writing output... [ 89%] topics/auth/default
writing output... [ 89%] topics/auth/index
writing output... [ 90%] topics/auth/passwords
writing output... [ 90%] topics/cache
writing output... [ 90%] topics/checks
writing output... [ 90%] topics/class-based-views/generic-display
writing output... [ 90%] topics/class-based-views/generic-editing
writing output... [ 91%] topics/class-based-views/index
writing output... [ 91%] topics/class-based-views/intro
writing output... [ 91%] topics/class-based-views/mixins
writing output... [ 91%] topics/conditional-view-processing
writing output... [ 91%] topics/db/aggregation
writing output... [ 91%] topics/db/examples/index
writing output... [ 92%] topics/db/examples/many_to_many
writing output... [ 92%] topics/db/examples/many_to_one
writing output... [ 92%] topics/db/examples/one_to_one
writing output... [ 92%] topics/db/fixtures
writing output... [ 92%] topics/db/index
writing output... [ 92%] topics/db/instrumentation
writing output... [ 93%] topics/db/managers
writing output... [ 93%] topics/db/models
writing output... [ 93%] topics/db/multi-db
writing output... [ 93%] topics/db/optimization
writing output... [ 93%] topics/db/queries
writing output... [ 93%] topics/db/search
writing output... [ 94%] topics/db/sql
writing output... [ 94%] topics/db/tablespaces
writing output... [ 94%] topics/db/transactions
writing output... [ 94%] topics/email
writing output... [ 94%] topics/external-packages
writing output... [ 94%] topics/files
writing output... [ 95%] topics/forms/formsets
writing output... [ 95%] topics/forms/index
writing output... [ 95%] topics/forms/media
writing output... [ 95%] topics/forms/modelforms
writing output... [ 95%] topics/http/decorators
writing output... [ 95%] topics/http/file-uploads
writing output... [ 96%] topics/http/generic-views
writing output... [ 96%] topics/http/index
writing output... [ 96%] topics/http/middleware
writing output... [ 96%] topics/http/sessions
writing output... [ 96%] topics/http/shortcuts
writing output... [ 96%] topics/http/urls
writing output... [ 97%] topics/http/views
writing output... [ 97%] topics/i18n/formatting
writing output... [ 97%] topics/i18n/index
writing output... [ 97%] topics/i18n/timezones
writing output... [ 97%] topics/i18n/translation
writing output... [ 97%] topics/index
writing output... [ 98%] topics/install
writing output... [ 98%] topics/logging
writing output... [ 98%] topics/migrations
writing output... [ 98%] topics/pagination
writing output... [ 98%] topics/performance
writing output... [ 98%] topics/security
writing output... [ 99%] topics/serialization
writing output... [ 99%] topics/settings
writing output... [ 99%] topics/signals
writing output... [ 99%] topics/signing
writing output... [ 99%] topics/templates
writing output... [ 99%] topics/testing/advanced
writing output... [100%] topics/testing/index
writing output... [100%] topics/testing/overview
writing output... [100%] topics/testing/tools

/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-management-commands.txt:122: WARNING: py:mod reference target not found: argparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-management-commands.txt:208: WARNING: py:mod reference target not found: argparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-management-commands.txt:270: WARNING: py:class reference target not found: argparse.ArgumentParser [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-management-commands.txt:274: WARNING: py:class reference target not found: argparse.ArgumentParser [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-management-commands.txt:365: WARNING: py:func reference target not found: sys.exit [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-template-tags.txt:373: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/custom-template-tags.txt:670: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/deployment/wsgi/modwsgi.txt:51: WARNING: py:mod reference target not found: venv [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/error-reporting.txt:343: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/error-reporting.txt:349: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:27: WARNING: py:func reference target not found: logging.getLogger [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:46: WARNING: py:class reference target not found: logging.LogRecord [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:74: WARNING: py:class reference target not found: logging.LogRecord [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:77: WARNING: undefined label: 'logging-config-dictschema' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:85: WARNING: py:mod reference target not found: python:logging.config [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:112: WARNING: py:class reference target not found: logging.FileHandler [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:129: WARNING: py:mod reference target not found: logging.handlers [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:189: WARNING: py:class reference target not found: logging.LogRecord [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:211: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:211: WARNING: py:class reference target not found: string.Template [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:214: WARNING: undefined label: 'logrecord-attributes' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:214: WARNING: py:class reference target not found: logging.LogRecord [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/logging.txt:240: WARNING: py:func reference target not found: logging.getLogger [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/outputting-csv.txt:12: WARNING: py:mod reference target not found: csv [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/outputting-csv.txt:12: WARNING: py:mod reference target not found: csv [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/outputting-csv.txt:51: WARNING: term not in glossary: 'iterable' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/outputting-csv.txt:104: WARNING: py:mod reference target not found: csv [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/upgrade-version.txt:62: WARNING: 'envvar' reference target not found: PYTHONWARNINGS [ref.envvar]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/upgrade-version.txt:89: WARNING: py:mod reference target not found: venv [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/windows.txt:38: WARNING: unknown document: 'python:using/windows' [ref.doc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/windows.txt:53: WARNING: unknown document: 'python:tutorial/venv' [ref.doc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/howto/windows.txt:134: WARNING: 'envvar' reference target not found: PYTHONUTF8 [ref.envvar]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:62: WARNING: undefined label: 'old-string-formatting' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:62: WARNING: undefined label: 'f-strings' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:62: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertRaises [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertWarns [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertRaisesRegex [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertWarnsRegex [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:112: WARNING: py:meth reference target not found: unittest.TestCase.assertIs [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:112: WARNING: py:meth reference target not found: unittest.TestCase.assertTrue [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/coding-style.txt:112: WARNING: py:meth reference target not found: unittest.TestCase.assertFalse [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-code/unit-tests.txt:165: WARNING: 'envvar' reference target not found: PYTHONPATH [ref.envvar]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:60: WARNING: undefined label: 'sphinx:rst-index' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:218: WARNING: py:mod reference target not found: sphinx.ext.intersphinx [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:250: WARNING: rst:role reference target not found: rfc [ref.role]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:254: WARNING: rst:role reference target not found: pep [ref.role]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:258: WARNING: rst:role reference target not found: mimetype [ref.role]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:261: WARNING: rst:role reference target not found: envvar [ref.role]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:261: WARNING: rst:dir reference target not found: envvar [ref.dir]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:273: WARNING: undefined label: 'sphinx:rst-index' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:501: WARNING: rst:role reference target not found: doc [ref.role]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/contributing/writing-documentation.txt:501: WARNING: rst:role reference target not found: ref [ref.role]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/deprecation.txt:598: WARNING: py:mod reference target not found: optparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/deprecation.txt:598: WARNING: py:mod reference target not found: argparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/deprecation.txt:793: WARNING: py:class reference target not found: collections.OrderedDict [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/deprecation.txt:977: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/deprecation.txt:1011: WARNING: py:class reference target not found: warnings.catch_warnings [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/internals/deprecation.txt:1135: WARNING: py:class reference target not found: unittest.TextTestRunner [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/intro/contributing.txt:350: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/intro/reusable-apps.txt:36: WARNING: term not in glossary: 'package' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/intro/reusable-apps.txt:339: WARNING: unknown document: 'python:tutorial/venv' [ref.doc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/intro/tutorial01.txt:105: WARNING: undefined label: 'tut-packages' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/intro/tutorial01.txt:217: WARNING: undefined label: 'tut-searchpath' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/intro/tutorial02.txt:468: WARNING: py:mod reference target not found: datetime [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:52: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:132: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:137: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:140: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:145: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:224: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:229: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:232: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:237: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:326: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:329: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:334: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:343: WARNING: py:func reference target not found: time.strptime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strptime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:443: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:446: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:451: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:456: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/generic-date-based.txt:461: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:9: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:25: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:35: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:77: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:87: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:129: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:139: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:181: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/class-based-views/mixins-date-based.txt:193: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/admin/index.txt:2829: WARNING: py:class reference target not found: weakref.WeakSet [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/gis/gdal.txt:1231: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/gis/gdal.txt:1287: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/gis/geoip2.txt:161: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/gis/install/index.txt:441: WARNING: unknown document: 'python:tutorial/venv' [ref.doc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/gis/install/index.txt:457: WARNING: py:func reference target not found: ctypes.util.find_library [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/gis/tutorial.txt:324: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/index.txt:5: WARNING: undefined label: 'tut-batteries-included' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/postgres/fields.txt:582: WARNING: undefined label: 'psycopg:adapt-range' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/postgres/fields.txt:915: WARNING: py:func reference target not found: psycopg:psycopg.types.range.register_range [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/sitemaps.txt:124: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/sitemaps.txt:129: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/sitemaps.txt:144: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/sitemaps.txt:179: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/sitemaps.txt:183: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/sitemaps.txt:278: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/staticfiles.txt:505: WARNING: py:mod reference target not found: mimetypes [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/syndication.txt:1001: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/syndication.txt:1002: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/contrib/syndication.txt:1065: WARNING: py:class reference target not found: xml.sax.saxutils.XMLGenerator [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/databases.txt:262: WARNING: undefined label: 'psycopg:client-side-binding-cursors' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/databases.txt:262: WARNING: undefined label: 'psycopg:server-side-binding' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/databases.txt:306: WARNING: undefined label: 'psycopg:server-side-cursors' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/databases.txt:911: WARNING: py:mod reference target not found: sqlite3 [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:188: WARNING: py:mod reference target not found: glob [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:643: WARNING: py:mod reference target not found: glob [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:731: WARNING: undefined label: 'python:identifiers' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1092: WARNING: 'envvar' reference target not found: PYTHONSTARTUP [ref.envvar]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1113: WARNING: py:func reference target not found: select.select [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1482: WARNING: py:func reference target not found: multiprocessing.cpu_count [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1488: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1512: WARNING: py:mod reference target not found: pdb [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1523: WARNING: undefined label: 'python:pickle-picklable' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1541: WARNING: unknown option: 'unittest.-k' [ref.option]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1551: WARNING: unknown option: 'unittest.-b' [ref.option]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1556: WARNING: py:func reference target not found: faulthandler.enable [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/django-admin.txt:1811: WARNING: 'envvar' reference target not found: PYTHONPATH [ref.envvar]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/exceptions.txt:349: WARNING: undefined label: 'bltin-exceptions' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/file.txt:15: WARNING: term not in glossary: 'file object' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/file.txt:32: WARNING: term not in glossary: 'file object' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/file.txt:36: WARNING: term not in glossary: 'file object' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/file.txt:51: WARNING: py:func reference target not found: python:open [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/storage.txt:83: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/storage.txt:83: WARNING: py:func reference target not found: os.path.getctime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/storage.txt:150: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/storage.txt:179: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/storage.txt:188: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/files/storage.txt:210: WARNING: py:mod reference target not found: os.path [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:443: WARNING: term not in glossary: 'iterable' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:578: WARNING: py:class reference target not found: python:datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:579: WARNING: py:attr reference target not found: datetime.timedelta.min [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:579: WARNING: py:attr reference target not found: datetime.timedelta.max [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:877: WARNING: py:class reference target not found: json.JSONEncoder [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:877: WARNING: py:class reference target not found: python:uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:886: WARNING: py:class reference target not found: json.JSONDecoder [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:892: WARNING: py:class reference target not found: json.JSONDecodeError [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:1107: WARNING: py:class reference target not found: python:uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/fields.txt:1110: WARNING: py:class reference target not found: python:uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/widgets.txt:258: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/widgets.txt:258: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/forms/widgets.txt:413: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/logging.txt:15: WARNING: py:mod reference target not found: logging [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/logging.txt:25: WARNING: undefined label: 'logging-config-dictschema' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/logging.txt:167: WARNING: py:class reference target not found: socket.socket [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/logging.txt:276: WARNING: py:mod reference target not found: python:logging.handlers [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:7: WARNING: unknown keyword: 'if' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:7: WARNING: unknown keyword: 'elif' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:7: WARNING: unknown keyword: 'else' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:106: WARNING: unknown keyword: 'if' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:106: WARNING: unknown keyword: 'elif' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:106: WARNING: unknown keyword: 'else' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:169: WARNING: unknown keyword: 'if' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:169: WARNING: unknown keyword: 'elif' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/conditional-expressions.txt:169: WARNING: unknown keyword: 'else' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/database-functions.txt:250: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/database-functions.txt:582: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/database-functions.txt:1454: WARNING: py:func reference target not found: chr [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/database-functions.txt:1623: WARNING: py:func reference target not found: ord [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/expressions.txt:525: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/expressions.txt:544: WARNING: unknown keyword: 'if' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/expressions.txt:544: WARNING: unknown keyword: 'elif' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/expressions.txt:544: WARNING: unknown keyword: 'else' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/expressions.txt:1031: WARNING: py:data reference target not found: NotImplemented [ref.data]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:89: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:223: WARNING: py:mod reference target not found: enum [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:245: WARNING: py:func reference target not found: enum.unique [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:296: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:699: WARNING: py:meth reference target not found: datetime.date.today [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:743: WARNING: py:class reference target not found: decimal.Decimal [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:785: WARNING: py:class reference target not found: python:datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:823: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:823: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:904: WARNING: py:func reference target not found: time.strftime [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:1143: WARNING: py:mod reference target not found: decimal [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:1246: WARNING: py:class reference target not found: json.JSONEncoder [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:1246: WARNING: py:class reference target not found: python:uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:1255: WARNING: py:class reference target not found: json.JSONDecoder [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:1427: WARNING: py:class reference target not found: python:uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/fields.txt:2153: WARNING: undefined label: 'descriptors' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/indexes.txt:163: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/instances.txt:718: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/instances.txt:812: WARNING: py:meth reference target not found: object.__hash__ [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:99: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:784: WARNING: py:func reference target not found: python:collections.namedtuple [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:847: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:851: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:889: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:895: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:902: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/models/querysets.txt:3737: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:448: WARNING: py:class reference target not found: xml.etree.ElementTree.ElementTree [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:535: WARNING: py:meth reference target not found: dict.setdefault [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:539: WARNING: py:meth reference target not found: dict.update [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:554: WARNING: py:meth reference target not found: dict.items [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:566: WARNING: py:meth reference target not found: dict.values [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:580: WARNING: py:func reference target not found: copy.deepcopy [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:791: WARNING: py:obj reference target not found: http.cookies.SimpleCookie [ref.obj]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:853: WARNING: py:class reference target not found: http.HTTPStatus [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:892: WARNING: py:meth reference target not found: dict.items [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:900: WARNING: py:class reference target not found: http.cookies.Morsel [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:903: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/request-response.txt:1079: WARNING: py:class reference target not found: http.HTTPStatus [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:1170: WARNING: undefined label: 'strftime-strptime-behavior' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:1214: WARNING: undefined label: 'strftime-strptime-behavior' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:1568: WARNING: py:meth reference target not found: python:ssl.SSLContext.wrap_socket [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:1637: WARNING: py:func reference target not found: os.chmod [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:2085: WARNING: undefined label: 'logging-config-dictschema' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:2862: WARNING: undefined label: 'strftime-strptime-behavior' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:2898: WARNING: py:func reference target not found: time.tzset [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/settings.txt:2922: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:1014: WARNING: py:func reference target not found: collections.namedtuple [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:1023: WARNING: py:func reference target not found: collections.namedtuple [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:1612: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:1628: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:2343: WARNING: py:func reference target not found: pprint.pprint [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:2453: WARNING: undefined label: 'old-string-formatting' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/templates/builtins.txt:2531: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/unicode.txt:156: WARNING: py:func reference target not found: urllib.parse.quote [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/unicode.txt:156: WARNING: py:func reference target not found: urllib.parse.quote_plus [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/urlresolvers.txt:79: WARNING: py:func reference target not found: urllib.parse.quote [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/urls.txt:65: WARNING: py:mod reference target not found: re [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/urls.txt:75: WARNING: py:func reference target not found: re.fullmatch [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:113: WARNING: py:mod reference target not found: datetime [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:124: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:128: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:135: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:137: WARNING: py:class reference target not found: datetime.timezone [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:142: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:280: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:490: WARNING: undefined label: 'descriptor-invocation' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:523: WARNING: py:func reference target not found: classmethod [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:619: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:733: WARNING: py:func reference target not found: urllib.parse.urlencode [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:846: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:900: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:904: WARNING: py:attr reference target not found: datetime.timezone.utc [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:904: WARNING: py:attr reference target not found: datetime.timezone.utc [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:909: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:912: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:918: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:928: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:938: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:958: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:968: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:968: WARNING: py:meth reference target not found: datetime.datetime.date [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:978: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:995: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:1000: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:1005: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:1005: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:1037: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/utils.txt:1037: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/validators.txt:89: WARNING: py:func reference target not found: re.search [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/validators.txt:99: WARNING: py:func reference target not found: re.search [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/validators.txt:99: WARNING: py:func reference target not found: re.compile [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/ref/validators.txt:122: WARNING: undefined label: 'python:contents-of-module-re' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/0.96.txt:207: WARNING: py:mod reference target not found: doctest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/0.96.txt:207: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.10.txt:447: WARNING: py:class reference target not found: io.TextIOWrapper [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.11.txt:285: WARNING: py:class reference target not found: io.TextIOWrapper [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.11.txt:392: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.11.txt:428: WARNING: py:meth reference target not found: python:unittest.TestCase.subTest [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.11.txt:777: WARNING: py:class reference target not found: io.StringIO [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.11.txt:777: WARNING: py:class reference target not found: io.BytesIO [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.2.txt:769: WARNING: py:mod reference target not found: warnings [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.3.txt:662: WARNING: py:mod reference target not found: warnings [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.4.txt:661: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.4.txt:851: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.4.txt:851: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.4.12.txt:12: WARNING: py:func reference target not found: functools.partial [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:391: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:483: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:495: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:499: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:515: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:521: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:608: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:773: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:773: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:778: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.txt:794: WARNING: py:func reference target not found: itertools.product [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.3.txt:31: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.3.txt:42: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.3.txt:42: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.3.txt:42: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.5.7.txt:12: WARNING: py:func reference target not found: functools.partial [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:207: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:423: WARNING: undefined label: 'doctest-unittest-api' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:427: WARNING: py:mod reference target not found: doctest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:504: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:504: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:508: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:804: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:815: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:815: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.txt:815: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.6.4.txt:16: WARNING: py:func reference target not found: functools.partial [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1051: WARNING: 'envvar' reference target not found: PYTHONPATH [ref.envvar]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1479: WARNING: py:mod reference target not found: logging.config [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1479: WARNING: py:mod reference target not found: importlib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1497: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1506: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1506: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.7.txt:1515: WARNING: py:class reference target not found: collections.OrderedDict [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:90: WARNING: py:class reference target not found: python:datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:108: WARNING: unknown keyword: 'if' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:108: WARNING: unknown keyword: 'elif' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:108: WARNING: unknown keyword: 'else' [ref.keyword]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:274: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:381: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:427: WARNING: py:mod reference target not found: argparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:747: WARNING: py:mod reference target not found: argparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:760: WARNING: py:mod reference target not found: optparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:760: WARNING: py:class reference target not found: argparse.ArgumentParser [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:1401: WARNING: py:mod reference target not found: argparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.txt:1401: WARNING: py:mod reference target not found: optparse [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.8.1.txt:13: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.9.txt:696: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.9.txt:701: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.9.txt:877: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.9.txt:889: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.9.txt:900: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/1.9.txt:1066: WARNING: py:data reference target not found: http.client.responses [ref.data]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/2.0.txt:347: WARNING: unknown option: '-b' [ref.option]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/2.1.txt:228: WARNING: py:meth reference target not found: unittest.TestCase.assertWarnsRegex [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/2.2.txt:505: WARNING: py:class reference target not found: datetime.timezone [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/2.2.1.txt:29: WARNING: py:class reference target not found: python:range [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/2.2.19.txt:12: WARNING: py:func reference target not found: urllib.parse.parse_qsl [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:162: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:164: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:286: WARNING: undefined label: 'descriptors' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:304: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:421: WARNING: py:class reference target not found: datetime.timezone [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:421: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:482: WARNING: py:meth reference target not found: unittest.TestCase.assertLogs [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:485: WARNING: py:func reference target not found: functools.lru_cache [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:491: WARNING: py:class reference target not found: contextlib.ContextDecorator [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:494: WARNING: py:func reference target not found: os.path.abspath [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:505: WARNING: py:func reference target not found: functools.partial [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:505: WARNING: py:class reference target not found: functools.partialmethod [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:546: WARNING: py:func reference target not found: html.escape [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:550: WARNING: unknown option: 'unittest.-k' [ref.option]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:555: WARNING: py:func reference target not found: urllib.parse.urlencode [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.quote [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.quote_plus [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.unquote [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.unquote_plus [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.txt:616: WARNING: py:func reference target not found: html.unescape [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.0.13.txt:12: WARNING: py:func reference target not found: urllib.parse.parse_qsl [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:256: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:279: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:304: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:410: WARNING: py:meth reference target not found: sqlite3.Connection.create_function [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:499: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:513: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:516: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.txt:516: WARNING: py:mod reference target not found: os.path [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.1.7.txt:12: WARNING: py:func reference target not found: urllib.parse.parse_qsl [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:238: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:241: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:377: WARNING: py:mod reference target not found: pathlib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:377: WARNING: py:class reference target not found: os.PathLike [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: decimal.Decimal [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:520: WARNING: py:func reference target not found: copy.deepcopy [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:525: WARNING: py:mod reference target not found: faulthandler [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:667: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:702: WARNING: py:func reference target not found: urllib.parse.parse_qsl [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:705: WARNING: py:meth reference target not found: unittest.TestCase.addCleanup [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:705: WARNING: py:meth reference target not found: unittest.TestCase.setUp [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.txt:760: WARNING: py:func reference target not found: copy.deepcopy [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/3.2.23.txt:12: WARNING: py:func reference target not found: python:unicodedata.normalize [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:34: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:37: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:42: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:292: WARNING: py:data reference target not found: sys.__interactivehook__ [ref.data]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:349: WARNING: py:data reference target not found: sys.stdout [ref.data]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:349: WARNING: py:func reference target not found: print [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:373: WARNING: undefined label: 'logger' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.0.txt:590: WARNING: py:attr reference target not found: datetime.timezone.utc [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.1.txt:369: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.1.txt:404: WARNING: py:mod reference target not found: multiprocessing [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.1.txt:538: WARNING: py:func reference target not found: unittest.expectedFailure [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.1.txt:699: WARNING: py:attr reference target not found: datetime.timezone.utc [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.1.txt:699: WARNING: py:attr reference target not found: datetime.timezone.utc [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.1.13.txt:12: WARNING: py:func reference target not found: python:unicodedata.normalize [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.2.txt:165: WARNING: py:class reference target not found: pathlib.Path [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.2.txt:477: WARNING: py:attr reference target not found: ssl.SSLContext.check_hostname [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.2.txt:477: WARNING: py:attr reference target not found: ssl.SSLContext.verify_mode [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.2.txt:565: WARNING: py:mod reference target not found: secrets [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/releases/4.2.7.txt:13: WARNING: py:func reference target not found: python:unicodedata.normalize [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/async.txt:252: WARNING: py:func reference target not found: asyncio.run [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/auth/passwords.txt:610: WARNING: py:meth reference target not found: difflib.SequenceMatcher.quick_ratio [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/cache.txt:370: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/models.txt:160: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/queries.txt:441: WARNING: undefined label: 'tut-keywordargs' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/queries.txt:731: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/queries.txt:1668: WARNING: unknown document: 'python:howto/descriptor' [ref.doc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/sql.txt:336: WARNING: py:func reference target not found: collections.namedtuple [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/transactions.txt:116: WARNING: term not in glossary: 'decorator' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/transactions.txt:126: WARNING: term not in glossary: 'context manager' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/transactions.txt:325: WARNING: py:func reference target not found: functools.partial [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/transactions.txt:406: WARNING: undefined label: 'psycopg:two-phase-commit' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/transactions.txt:635: WARNING: py:mod reference target not found: sqlite3 [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/db/transactions.txt:638: WARNING: py:mod reference target not found: sqlite3 [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:8: WARNING: py:mod reference target not found: smtplib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:59: WARNING: py:exc reference target not found: smtplib.SMTPException [ref.exc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:59: WARNING: py:mod reference target not found: smtplib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:59: WARNING: py:exc reference target not found: smtplib.SMTPException [ref.exc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:284: WARNING: py:class reference target not found: email.mime.base.MIMEBase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:323: WARNING: py:class reference target not found: email.mime.text.MIMEText [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:340: WARNING: py:class reference target not found: email.mime.base.MIMEBase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:356: WARNING: py:class reference target not found: email.message.Message [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/email.txt:511: WARNING: py:func reference target not found: socket.getdefaulttimeout [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/sessions.txt:283: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/sessions.txt:285: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/sessions.txt:340: WARNING: py:mod reference target not found: pickle [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/sessions.txt:698: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/urls.txt:43: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/urls.txt:128: WARNING: py:class reference target not found: uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/http/urls.txt:331: WARNING: term not in glossary: 'sequence' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:34: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:55: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:55: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:82: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:90: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:109: WARNING: py:mod reference target not found: zoneinfo [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:115: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:143: WARNING: py:meth reference target not found: datetime.datetime.fromtimestamp [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:143: WARNING: py:attr reference target not found: datetime.timezone.utc [ref.attr]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:160: WARNING: py:func reference target not found: zoneinfo.available_timezones [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:372: WARNING: py:class reference target not found: datetime.tzinfo [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:576: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:598: WARNING: py:meth reference target not found: datetime.datetime.date [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:598: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:598: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:635: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:635: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/timezones.txt:709: WARNING: py:func reference target not found: zoneinfo.available_timezones [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/translation.txt:131: WARNING: undefined label: 'f-strings' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/translation.txt:491: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/translation.txt:491: WARNING: py:meth reference target not found: str.format [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/i18n/translation.txt:1747: WARNING: undefined label: 'old-string-formatting' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/install.txt:142: WARNING: unknown document: 'python:tutorial/venv' [ref.doc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:21: WARNING: py:mod reference target not found: logging [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:123: WARNING: undefined label: 'python:logrecord-attributes' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:169: WARNING: undefined label: 'logging-config-dictschema' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:202: WARNING: undefined label: 'logging-config-dictschema' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:367: WARNING: undefined label: 'formatter-objects' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:389: WARNING: py:class reference target not found: logging.StreamHandler [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/logging.txt:420: WARNING: py:func reference target not found: logging.config.dictConfig [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:778: WARNING: py:func reference target not found: functools.partial [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:778: WARNING: py:class reference target not found: functools.partialmethod [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:780: WARNING: py:mod reference target not found: pathlib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:780: WARNING: py:class reference target not found: pathlib.PosixPath [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:780: WARNING: py:class reference target not found: pathlib.PurePosixPath [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:783: WARNING: py:class reference target not found: os.PathLike [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:783: WARNING: py:class reference target not found: os.DirEntry [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:783: WARNING: py:func reference target not found: os.fspath [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/migrations.txt:808: WARNING: py:class reference target not found: decimal.Decimal [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/performance.txt:210: WARNING: term not in glossary: 'generator' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/performance.txt:210: WARNING: term not in glossary: 'generator expression' [ref.term]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:266: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:266: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:295: WARNING: py:class reference target not found: json.JSONEncoder [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:298: WARNING: py:class reference target not found: datetime.datetime [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:302: WARNING: py:class reference target not found: datetime.date [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:305: WARNING: py:class reference target not found: datetime.time [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:308: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:313: WARNING: py:class reference target not found: decimal.Decimal [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/serialization.txt:313: WARNING: py:class reference target not found: uuid.UUID [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/signing.txt:119: WARNING: py:mod reference target not found: hashlib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/signing.txt:205: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/signing.txt:216: WARNING: py:class reference target not found: datetime.timedelta [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/advanced.txt:489: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/advanced.txt:597: WARNING: py:mod reference target not found: faulthandler [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/advanced.txt:611: WARNING: undefined label: 'logger' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/advanced.txt:672: WARNING: py:meth reference target not found: argparse.ArgumentParser.add_argument [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/index.txt:23: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:20: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:23: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:43: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:48: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:63: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:67: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:85: WARNING: undefined label: 'unittest-test-discovery' [ref.ref]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:231: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/overview.txt:339: WARNING: py:mod reference target not found: unittest [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:87: WARNING: py:mod reference target not found: urllib [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:266: WARNING: py:func reference target not found: json.dumps [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:305: WARNING: py:class reference target not found: io.StringIO [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:305: WARNING: py:class reference target not found: io.BytesIO [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:575: WARNING: py:func reference target not found: sys.exc_info [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:587: WARNING: py:func reference target not found: json.loads [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:655: WARNING: py:meth reference target not found: unittest.TestCase.assertRaises [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:688: WARNING: py:class reference target not found: http.cookies.SimpleCookie [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:688: WARNING: py:mod reference target not found: http.cookies [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:787: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:799: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:810: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:867: WARNING: py:exc reference target not found: unittest.SkipTest [ref.exc]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:976: WARNING: py:func reference target not found: copy.deepcopy [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1601: WARNING: py:class reference target not found: unittest.TestCase [ref.class]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1601: WARNING: py:meth reference target not found: unittest.TestCase.assertTrue [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1601: WARNING: py:meth reference target not found: unittest.TestCase.assertEqual [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1616: WARNING: py:meth reference target not found: unittest.TestCase.assertRaisesRegex [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1632: WARNING: py:meth reference target not found: unittest.TestCase.assertWarnsRegex [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1632: WARNING: py:meth reference target not found: unittest.TestCase.assertRaisesRegex [ref.meth]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:1885: WARNING: py:mod reference target not found: json [ref.mod]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:2167: WARNING: py:func reference target not found: unittest.skipIf [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:2167: WARNING: py:func reference target not found: unittest.skipUnless [ref.func]
/builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/docs/topics/testing/tools.txt:2172: WARNING: py:func reference target not found: unittest.skipIf [ref.func]
generating indices... genindex py-modindex done
highlighting module code... [  1%] asgiref.sync
highlighting module code... [  2%] django
highlighting module code... [  2%] django.apps.config
highlighting module code... [  3%] django.conf.urls.i18n
highlighting module code... [  4%] django.contrib.admin
highlighting module code... [  5%] django.contrib.admin.decorators
highlighting module code... [  5%] django.contrib.admin.options
highlighting module code... [  6%] django.contrib.admin.sites
highlighting module code... [  7%] django.contrib.admin.views.decorators
highlighting module code... [  8%] django.contrib.auth
highlighting module code... [  8%] django.contrib.auth.context_processors
highlighting module code... [  9%] django.contrib.auth.decorators
highlighting module code... [ 10%] django.contrib.auth.hashers
highlighting module code... [ 11%] django.contrib.auth.password_validation
highlighting module code... [ 11%] django.contrib.flatpages.sitemaps
highlighting module code... [ 12%] django.contrib.gis.feeds
highlighting module code... [ 13%] django.contrib.gis.measure
highlighting module code... [ 14%] django.contrib.messages.api
highlighting module code... [ 15%] django.contrib.messages.middleware
highlighting module code... [ 15%] django.contrib.postgres.constraints
highlighting module code... [ 16%] django.contrib.postgres.functions
highlighting module code... [ 17%] django.contrib.postgres.indexes
highlighting module code... [ 18%] django.contrib.postgres.search
highlighting module code... [ 18%] django.contrib.postgres.validators
highlighting module code... [ 19%] django.contrib.sessions.exceptions
highlighting module code... [ 20%] django.contrib.sessions.middleware
highlighting module code... [ 21%] django.contrib.sitemaps
highlighting module code... [ 21%] django.contrib.sites.middleware
highlighting module code... [ 22%] django.core.checks.messages
highlighting module code... [ 23%] django.core.exceptions
highlighting module code... [ 24%] django.core.files.base
highlighting module code... [ 24%] django.core.files.images
highlighting module code... [ 25%] django.core.files.storage
highlighting module code... [ 26%] django.core.files.storage.base
highlighting module code... [ 27%] django.core.files.storage.filesystem
highlighting module code... [ 27%] django.core.files.storage.memory
highlighting module code... [ 28%] django.core.files.uploadedfile
highlighting module code... [ 29%] django.core.files.uploadhandler
highlighting module code... [ 30%] django.core.mail
highlighting module code... [ 31%] django.core.mail.message
highlighting module code... [ 31%] django.core.management.base
highlighting module code... [ 32%] django.core.paginator
highlighting module code... [ 33%] django.core.signing
highlighting module code... [ 34%] django.core.validators
highlighting module code... [ 34%] django.db.backends.base.schema
highlighting module code... [ 35%] django.db.migrations.operations.fields
highlighting module code... [ 36%] django.db.migrations.operations.models
highlighting module code... [ 37%] django.db.migrations.operations.special
highlighting module code... [ 37%] django.db.models.aggregates
highlighting module code... [ 38%] django.db.models.base
highlighting module code... [ 39%] django.db.models.constraints
highlighting module code... [ 40%] django.db.models.deletion
highlighting module code... [ 40%] django.db.models.expressions
highlighting module code... [ 41%] django.db.models.fields
highlighting module code... [ 42%] django.db.models.fields.files
highlighting module code... [ 43%] django.db.models.fields.json
highlighting module code... [ 44%] django.db.models.fields.related
highlighting module code... [ 44%] django.db.models.functions.comparison
highlighting module code... [ 45%] django.db.models.functions.datetime
highlighting module code... [ 46%] django.db.models.functions.math
highlighting module code... [ 47%] django.db.models.functions.text
highlighting module code... [ 47%] django.db.models.functions.window
highlighting module code... [ 48%] django.db.models.indexes
highlighting module code... [ 49%] django.db.models.lookups
highlighting module code... [ 50%] django.db.models.manager
highlighting module code... [ 50%] django.db.models.options
highlighting module code... [ 51%] django.db.models.query
highlighting module code... [ 52%] django.db.models.query_utils
highlighting module code... [ 53%] django.db.transaction
highlighting module code... [ 53%] django.db.utils
highlighting module code... [ 54%] django.dispatch.dispatcher
highlighting module code... [ 55%] django.forms.boundfield
highlighting module code... [ 56%] django.forms.fields
highlighting module code... [ 56%] django.forms.forms
highlighting module code... [ 57%] django.forms.formsets
highlighting module code... [ 58%] django.forms.models
highlighting module code... [ 59%] django.forms.renderers
highlighting module code... [ 60%] django.forms.widgets
highlighting module code... [ 60%] django.http.request
highlighting module code... [ 61%] django.http.response
highlighting module code... [ 62%] django.middleware.cache
highlighting module code... [ 63%] django.middleware.clickjacking
highlighting module code... [ 63%] django.middleware.common
highlighting module code... [ 64%] django.middleware.csrf
highlighting module code... [ 65%] django.middleware.gzip
highlighting module code... [ 66%] django.middleware.http
highlighting module code... [ 66%] django.middleware.locale
highlighting module code... [ 67%] django.middleware.security
highlighting module code... [ 68%] django.shortcuts
highlighting module code... [ 69%] django.template.backends.django
highlighting module code... [ 69%] django.template.backends.jinja2
highlighting module code... [ 70%] django.template.base
highlighting module code... [ 71%] django.template.context
highlighting module code... [ 72%] django.template.context_processors
highlighting module code... [ 73%] django.template.engine
highlighting module code... [ 73%] django.template.exceptions
highlighting module code... [ 74%] django.template.loader
highlighting module code... [ 75%] django.template.loaders.base
highlighting module code... [ 76%] django.template.response
highlighting module code... [ 76%] django.test.client
highlighting module code... [ 77%] django.test.runner
highlighting module code... [ 78%] django.test.testcases
highlighting module code... [ 79%] django.test.utils
highlighting module code... [ 79%] django.urls.base
highlighting module code... [ 80%] django.urls.conf
highlighting module code... [ 81%] django.urls.converters
highlighting module code... [ 82%] django.urls.exceptions
highlighting module code... [ 82%] django.urls.resolvers
highlighting module code... [ 83%] django.utils.cache
highlighting module code... [ 84%] django.utils.dateparse
highlighting module code... [ 85%] django.utils.decorators
highlighting module code... [ 85%] django.utils.encoding
highlighting module code... [ 86%] django.utils.feedgenerator
highlighting module code... [ 87%] django.utils.functional
highlighting module code... [ 88%] django.utils.html
highlighting module code... [ 89%] django.utils.http
highlighting module code... [ 89%] django.utils.log
highlighting module code... [ 90%] django.utils.module_loading
highlighting module code... [ 91%] django.utils.safestring
highlighting module code... [ 92%] django.utils.text
highlighting module code... [ 92%] django.utils.timezone
highlighting module code... [ 93%] django.utils.translation
highlighting module code... [ 94%] django.views.debug
highlighting module code... [ 95%] django.views.decorators.cache
highlighting module code... [ 95%] django.views.decorators.common
highlighting module code... [ 96%] django.views.decorators.csrf
highlighting module code... [ 97%] django.views.decorators.debug
highlighting module code... [ 98%] django.views.decorators.http
highlighting module code... [ 98%] django.views.decorators.vary
highlighting module code... [ 99%] django.views.generic.dates
highlighting module code... [100%] django.views.i18n

writing additional pages... search done
copying images... [  4%] howto/_images/postmortem.png
copying images... [  8%] howto/_images/template-lines.png
copying images... [ 12%] internals/_images/triage_process.svg
copying images... [ 17%] intro/_images/admin01.png
copying images... [ 21%] intro/_images/admin02.png
copying images... [ 25%] intro/_images/admin03t.png
copying images... [ 29%] intro/_images/admin04t.png
copying images... [ 33%] intro/_images/admin05t.png
copying images... [ 38%] intro/_images/admin06t.png
copying images... [ 42%] intro/_images/admin07.png
copying images... [ 46%] intro/_images/admin08t.png
copying images... [ 50%] intro/_images/admin09.png
copying images... [ 54%] intro/_images/admin10t.png
copying images... [ 58%] intro/_images/admin14t.png
copying images... [ 62%] intro/_images/admin11t.png
copying images... [ 67%] intro/_images/admin12t.png
copying images... [ 71%] intro/_images/admin13t.png
copying images... [ 75%] ref/contrib/admin/_images/admin-actions.png
copying images... [ 79%] ref/contrib/admin/_images/adding-actions-to-the-modeladmin.png
copying images... [ 83%] ref/contrib/admin/_images/actions-as-modeladmin-methods.png
copying images... [ 88%] ref/contrib/admin/_images/list_filter.png
copying images... [ 92%] ref/contrib/admin/_images/fieldsets.png
copying images... [ 96%] ref/contrib/admin/_images/raw_id_fields.png
copying images... [100%] topics/testing/_images/django_unittest_classes_hierarchy.svg

dumping search index in English (code: en)... done
dumping object inventory... done
writing templatebuiltins.js...
build succeeded, 535 warnings.

The HTML pages are in _build/html.

Build finished. The HTML pages are in _build/html.
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/doc/python3-django4.2-doc
+ cp -ar docs/_build/html/_images docs/_build/html/_modules docs/_build/html/_sources docs/_build/html/_static docs/_build/html/contents.html docs/_build/html/faq docs/_build/html/genindex.html docs/_build/html/glossary.html docs/_build/html/howto docs/_build/html/index.html docs/_build/html/internals docs/_build/html/intro docs/_build/html/misc docs/_build/html/objects.inv docs/_build/html/py-modindex.html docs/_build/html/ref docs/_build/html/releases docs/_build/html/search.html docs/_build/html/searchindex.js docs/_build/html/templatebuiltins.js docs/_build/html/topics /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/doc/python3-django4.2-doc/
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/man/man1/
+ cp -p docs/man/django-admin.1 /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/man/man1/
+ mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions
+ install -m 0644 -p extras/django_bash_completion /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions/django-admin.py
+ for file in django-admin django-admin-3 django-admin-3.13 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions/django-admin
+ for file in django-admin django-admin-3 django-admin-3.13 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions/django-admin-3
+ for file in django-admin django-admin-3 django-admin-3.13 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions/django-admin-3.13
+ for file in django-admin django-admin-3 django-admin-3.13 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions/python3-django-admin
+ for file in django-admin django-admin-3 django-admin-3.13 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/bash-completion/completions/manage.py
+ ln -s ./django-admin /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/django-admin-3
+ ln -s ./django-admin /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/django-admin-3.13
+ ln -s ./django-admin /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin/python3-django-admin
+ find /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT -name '*.po'
+ xargs rm -f
+ sed -i '/.po$/d' /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-files
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-strip /usr/bin/strip
+ /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+ /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/check-rpaths
+ /usr/lib/rpm/redhat/brp-mangle-shebangs
+ /usr/lib/rpm/brp-remove-la-files
+ /usr/lib/rpm/redhat/brp-python-rpm-in-distinfo
+ env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j4
Bytecompiling .py files below /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13 using python3.13
+ /usr/lib/rpm/redhat/brp-python-hardlink
+ /usr/bin/add-determinism --brp -j4 /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/apps/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ar/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ar/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ar_DZ/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ar_DZ/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/apps/__pycache__/config.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/az/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/az/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/bg/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/bg/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/bn/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/bn/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/bs/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/bs/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ca/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ckb/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ckb/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ca/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/cs/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/cy/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/cs/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/cy/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/da/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/de/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/da/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/de_CH/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/de/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/el/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/de_CH/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/en/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/el/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/en_AU/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/apps/__pycache__/registry.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/en_AU/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/eo/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/en_GB/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/eo/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_AR/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_AR/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_CO/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_MX/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_CO/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_NI/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_MX/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_PR/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_NI/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/et/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/es_PR/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/et/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/eu/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fa/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/eu/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fi/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fa/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fr/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fi/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fy/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fr/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/fy/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ga/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ga/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/gd/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/gl/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/gd/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/he/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/gl/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/he/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/hi/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/hr/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/hi/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/hu/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/hr/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/hu/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/id/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ig/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/id/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ig/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/is/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/is/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/it/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/en/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/it/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/en_GB/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ja/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ka/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ja/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/km/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ka/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/km/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/kn/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ko/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/kn/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ky/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ko/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/lt/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ky/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/lv/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/lt/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/lv/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/mk/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ml/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/mk/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ml/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/mn/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ms/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/mn/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/nb/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ms/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/nl/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/nl/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/nn/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/nn/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/pl/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/pl/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/pt/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/pt/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/pt_BR/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/pt_BR/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ro/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ro/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/nb/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ru/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sk/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ru/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sk/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sl/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sq/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sq/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sl/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sr/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sr_Latn/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sr/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sv/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sr_Latn/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ta/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/sv/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/ta/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/te/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/te/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/tg/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/tg/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/th/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/th/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/tk/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/tk/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/tr/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/uk/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/tr/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/uz/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/uk/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/vi/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/uz/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/zh_Hans/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/vi/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/zh_Hant/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/zh_Hans/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/zh_Hant/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/urls/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/urls/__pycache__/i18n.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/urls/__pycache__/static.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/__pycache__/global_settings.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/locale/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/migrations/__pycache__/0002_logentry_remove_auto_add.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/migrations/__pycache__/0003_logentry_add_action_flag_choices.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/conf/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/templatetags/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/templatetags/__pycache__/admin_urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/templatetags/__pycache__/admin_modify.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/templatetags/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/views/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/templatetags/__pycache__/log.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/views/__pycache__/decorators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/views/__pycache__/autocomplete.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/templatetags/__pycache__/admin_list.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/actions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/decorators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/views/__pycache__/main.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/filters.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/helpers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/tests.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/sites.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/widgets.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admindocs/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admindocs/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admindocs/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admindocs/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admin/__pycache__/options.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admindocs/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/handlers/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/handlers/__pycache__/modwsgi.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/management/commands/__pycache__/changepassword.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0002_alter_permission_name_max_length.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0003_alter_user_email_max_length.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0004_alter_user_username_opts.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0005_alter_user_last_login_null.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0006_require_contenttypes_0002.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0007_alter_validators_add_error_messages.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0008_alter_user_username_max_length.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0009_alter_user_last_name_max_length.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0010_alter_group_name_max_length.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0012_alter_user_first_name_max_length.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/migrations/__pycache__/0011_update_proxy_permissions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/management/commands/__pycache__/createsuperuser.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/admindocs/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/context_processors.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/base_user.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/decorators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/mixins.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/backends.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/password_validation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/validators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/tokens.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/hashers.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/management/commands/__pycache__/remove_stale_contenttypes.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/migrations/__pycache__/0002_remove_content_type_name.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/templatetags/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/templatetags/__pycache__/flatpages.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/sitemaps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/admin/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/flatpages/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/admin/__pycache__/widgets.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/base/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/admin/__pycache__/options.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/base/__pycache__/adapter.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/base/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/base/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/mysql/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/mysql/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/mysql/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/mysql/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/base/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/mysql/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/mysql/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/adapter.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/contenttypes/__pycache__/fields.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/auth/__pycache__/hashers.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/adapter.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/const.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/oracle/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/pgraster.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/adapter.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/client.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/sql/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/sql/__pycache__/conversion.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/postgis/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/__pycache__/aggregates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/backends/spatialite/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/__pycache__/proxy.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/forms/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/forms/__pycache__/fields.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/__pycache__/fields.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/__pycache__/lookups.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/ds.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/errcheck.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/generation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/forms/__pycache__/widgets.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/geom.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/raster.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/raster/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/prototypes/__pycache__/srs.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/raster/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/raster/__pycache__/const.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/raster/__pycache__/band.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/db/models/__pycache__/functions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/datasource.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/driver.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/error.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/envelope.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/feature.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/geomtype.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/field.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/layer.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/libgdal.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geoip2/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/raster/__pycache__/source.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geoip2/__pycache__/resources.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geoip2/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/coordseq.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/errcheck.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/geom.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/misc.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/predicates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/prepared.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/geometries.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/topology.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/threadsafe.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/prototypes/__pycache__/io.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/gdal/__pycache__/srs.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/collections.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/error.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/factory.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/io.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/libgeos.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/linestring.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/coordseq.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/point.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/prepared.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/management/commands/__pycache__/inspectdb.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/polygon.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/mutable_list.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/serializers/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/sitemaps/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/sitemaps/__pycache__/kml.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/serializers/__pycache__/geojson.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/management/commands/__pycache__/ogrinspect.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/sitemaps/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/utils/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/utils/__pycache__/ogrinfo.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/utils/__pycache__/ogrinspect.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/utils/__pycache__/srs.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/geometry.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/geos/__pycache__/geometry.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/ptr.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/utils/__pycache__/layermapping.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/feeds.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/shortcuts.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/humanize/templatetags/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/humanize/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/humanize/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/storage/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/humanize/templatetags/__pycache__/humanize.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/storage/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/storage/__pycache__/cookie.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/storage/__pycache__/session.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/storage/__pycache__/fallback.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/constants.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/context_processors.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/api.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/aggregates/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/messages/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/aggregates/__pycache__/mixins.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/aggregates/__pycache__/statistics.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/gis/__pycache__/measure.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/citext.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/aggregates/__pycache__/general.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/jsonb.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/forms/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/hstore.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/forms/__pycache__/hstore.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/forms/__pycache__/array.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/forms/__pycache__/ranges.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/array.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/expressions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/functions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/constraints.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/lookups.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/indexes.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/fields/__pycache__/ranges.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/serializers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/migrations/__pycache__/0002_alter_redirect_new_path_help_text.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/validators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/redirects/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/cache.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/cached_db.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/db.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/signed_cookies.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/postgres/__pycache__/search.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/file.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/management/commands/__pycache__/clearsessions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/backends/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/base_session.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/serializers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sitemaps/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sessions/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sitemaps/management/commands/__pycache__/ping_google.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sitemaps/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sitemaps/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/migrations/__pycache__/0002_alter_domain_unique.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/management.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/middleware.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/managers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/requests.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/shortcuts.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sites/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sitemaps/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/sitemaps/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/management/commands/__pycache__/runserver.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/management/commands/__pycache__/findstatic.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/handlers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/testing.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/management/commands/__pycache__/collectstatic.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/syndication/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/syndication/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/finders.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/storage.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/syndication/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/dummy.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/contrib/staticfiles/__pycache__/storage.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/db.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/filebased.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/locmem.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/compatibility/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/compatibility/__pycache__/django_4_0.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/security/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/memcached.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/security/__pycache__/csrf.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/security/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/async_checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/security/__pycache__/sessions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/database.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/files.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/caches.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/cache/backends/__pycache__/redis.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/templates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/messages.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/registry.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/model_checks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/storage/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/translation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/storage/__pycache__/handler.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/storage/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/storage/__pycache__/mixins.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/checks/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/images.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/storage/__pycache__/filesystem.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/move.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/locks.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/temp.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/storage/__pycache__/memory.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/handlers/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/uploadedfile.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/uploadhandler.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/files/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/handlers/__pycache__/exception.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/handlers/__pycache__/asgi.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/handlers/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/console.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/dummy.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/locmem.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/filebased.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/backends/__pycache__/smtp.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/handlers/__pycache__/wsgi.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/check.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/dbshell.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/compilemessages.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/createcachetable.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/diffsettings.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/flush.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/mail/__pycache__/message.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/dumpdata.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/inspectdb.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/loaddata.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/optimizemigration.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/migrate.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/runserver.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/sendtestemail.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/shell.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/makemessages.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/sqlflush.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/showmigrations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/makemigrations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/sqlmigrate.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/sqlsequencereset.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/startproject.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/startapp.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/test.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/squashmigrations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/commands/__pycache__/testserver.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/__pycache__/color.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/__pycache__/sql.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/__pycache__/templates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/jsonl.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/json.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/management/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/pyyaml.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/servers/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/python.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/asgi.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/servers/__pycache__/basehttp.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/paginator.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/wsgi.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/signing.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/client.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/serializers/__pycache__/xml_serializer.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/core/__pycache__/validators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/creation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/validation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/dummy/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/dummy/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/dummy/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/client.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/compiler.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/creation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/validation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/client.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/mysql/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/functions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/base/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/creation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/validation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/client.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/creation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/psycopg_any.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/oracle/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/postgresql/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/client.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/_functions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/creation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/features.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/introspection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/schema.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/sqlite3/__pycache__/operations.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/operations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/backends/__pycache__/ddl_references.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/operations/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/operations/__pycache__/special.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/operations/__pycache__/fields.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/executor.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/graph.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/loader.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/migration.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/optimizer.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/recorder.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/questioner.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/operations/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/autodetector.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/writer.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/serializer.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/graph.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/state.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/state.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/migrations/__pycache__/autodetector.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/files.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/proxy.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/mixins.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/json.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/related_lookups.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/reverse_related.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/related_lookups.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/related_descriptors.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/related.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/__init__.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/comparison.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/datetime.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/mixins.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/math.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/window.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/datetime.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/functions/__pycache__/text.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/constants.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/datastructures.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/related.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/subqueries.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/where.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/compiler.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/query.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/fields/__pycache__/__init__.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/where.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/aggregates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/constants.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/constraints.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/deletion.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/query.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/enums.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/sql/__pycache__/compiler.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/indexes.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/manager.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/lookups.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/base.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/options.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/utils.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/query_utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/expressions.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/base.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/query.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/utils.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/__pycache__/transaction.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/dispatch/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/dispatch/__pycache__/dispatcher.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/expressions.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/db/models/__pycache__/query.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/boundfield.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/formsets.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/renderers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/http/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/http/__pycache__/cookie.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/http/__pycache__/multipartparser.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/fields.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/forms/__pycache__/widgets.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/http/__pycache__/request.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/cache.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/clickjacking.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/http/__pycache__/multipartparser.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/gzip.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/common.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/http.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/locale.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/security.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/backends/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/backends/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/csrf.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/backends/__pycache__/dummy.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/backends/__pycache__/django.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/backends/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/loaders/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/loaders/__pycache__/app_directories.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/http/__pycache__/response.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/loaders/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/backends/__pycache__/jinja2.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/loaders/__pycache__/filesystem.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/loaders/__pycache__/cached.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/loaders/__pycache__/locmem.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/autoreload.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/middleware/__pycache__/csrf.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/context_processors.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/context.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/engine.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/defaultfilters.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/loader.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/library.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/loader_tags.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/base.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/response.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/templatetags/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/templatetags/__pycache__/cache.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/defaulttags.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/smartif.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/templatetags/__pycache__/l10n.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/templatetags/__pycache__/static.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/templatetags/__pycache__/tz.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/templatetags/__pycache__/i18n.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/html.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/template/__pycache__/base.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/selenium.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/client.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/utils.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/runner.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/client.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/testcases.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/conf.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/runner.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/converters.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/utils.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/translation/__pycache__/reloader.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/translation/__pycache__/template.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/translation/__pycache__/trans_null.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/translation/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/_os.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/test/__pycache__/testcases.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/archive.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/asyncio.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/urls/__pycache__/resolvers.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/baseconv.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/translation/__pycache__/trans_real.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/connection.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/crypto.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/cache.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/dateparse.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/dates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/datetime_safe.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/deconstruct.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/dateformat.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/datastructures.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/decorators.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/duration.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/deprecation.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/encoding.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/autoreload.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/formats.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/hashable.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/http.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/feedgenerator.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/inspect.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/html.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/ipv6.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/itercompat.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/functional.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/jslex.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/module_loading.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/numberformat.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/lorem_ipsum.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/safestring.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/log.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/regex_helper.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/timesince.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/termcolors.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/topological_sort.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/version.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/timezone.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/tree.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/xmlutils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/text.cpython-313.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/version.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/cache.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/clickjacking.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/common.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/csrf.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/gzip.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/debug.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/regex_helper.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/vary.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/generic/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/decorators/__pycache__/http.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/utils/__pycache__/text.cpython-313.opt-1.pyc: replacing with normalized version
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/generic/__pycache__/detail.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/generic/__pycache__/base.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/generic/__pycache__/list.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/generic/__pycache__/edit.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/__pycache__/csrf.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/__pycache__/defaults.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/__pycache__/static.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/__pycache__/__main__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/__pycache__/i18n.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/__pycache__/shortcuts.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/generic/__pycache__/dates.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages/django/views/__pycache__/debug.cpython-313.pyc: rewriting with normalized contents
Scanned 2745 directories and 5532 files,
               processed 1782 inodes,
               897 modified (52 replaced + 845 rewritten),
               0 unsupported format, 0 errors
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.wlPh4W
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd Django-4.2.20
+ '[' '!' -f /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-modules ']'
+ PATH=/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin
+ PYTHONPATH=/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib64/python3.13/site-packages:/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages
+ _PYTHONSITE=/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib64/python3.13/site-packages:/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/lib/python3.13/site-packages
+ PYTHONDONTWRITEBYTECODE=1
+ /usr/bin/python3 -sP /usr/lib/rpm/redhat/import_all_modules.py -f /builddir/build/BUILD/python-django4.2-4.2.20-build/python-django4.2-4.2.20-2.fc43.x86_64-pyproject-modules -e 'django.contrib.*' -e django.core.serializers.pyyaml -e 'django.db.backends.mysql*' -e 'django.db.backends.oracle*' -e 'django.db.backends.postgresql*'
Check import: django
Check import: django.apps
Check import: django.apps.config
Check import: django.apps.registry
Check import: django.conf
Check import: django.conf.global_settings
Check import: django.conf.locale
Check import: django.conf.locale.ar
Check import: django.conf.locale.ar.formats
Check import: django.conf.locale.ar_DZ
Check import: django.conf.locale.ar_DZ.formats
Check import: django.conf.locale.az
Check import: django.conf.locale.az.formats
Check import: django.conf.locale.bg
Check import: django.conf.locale.bg.formats
Check import: django.conf.locale.bn
Check import: django.conf.locale.bn.formats
Check import: django.conf.locale.bs
Check import: django.conf.locale.bs.formats
Check import: django.conf.locale.ca
Check import: django.conf.locale.ca.formats
Check import: django.conf.locale.ckb
Check import: django.conf.locale.ckb.formats
Check import: django.conf.locale.cs
Check import: django.conf.locale.cs.formats
Check import: django.conf.locale.cy
Check import: django.conf.locale.cy.formats
Check import: django.conf.locale.da
Check import: django.conf.locale.da.formats
Check import: django.conf.locale.de
Check import: django.conf.locale.de.formats
Check import: django.conf.locale.de_CH
Check import: django.conf.locale.de_CH.formats
Check import: django.conf.locale.el
Check import: django.conf.locale.el.formats
Check import: django.conf.locale.en
Check import: django.conf.locale.en.formats
Check import: django.conf.locale.en_AU
Check import: django.conf.locale.en_AU.formats
Check import: django.conf.locale.en_GB
Check import: django.conf.locale.en_GB.formats
Check import: django.conf.locale.eo
Check import: django.conf.locale.eo.formats
Check import: django.conf.locale.es
Check import: django.conf.locale.es.formats
Check import: django.conf.locale.es_AR
Check import: django.conf.locale.es_AR.formats
Check import: django.conf.locale.es_CO
Check import: django.conf.locale.es_CO.formats
Check import: django.conf.locale.es_MX
Check import: django.conf.locale.es_MX.formats
Check import: django.conf.locale.es_NI
Check import: django.conf.locale.es_NI.formats
Check import: django.conf.locale.es_PR
Check import: django.conf.locale.es_PR.formats
Check import: django.conf.locale.et
Check import: django.conf.locale.et.formats
Check import: django.conf.locale.eu
Check import: django.conf.locale.eu.formats
Check import: django.conf.locale.fa
Check import: django.conf.locale.fa.formats
Check import: django.conf.locale.fi
Check import: django.conf.locale.fi.formats
Check import: django.conf.locale.fr
Check import: django.conf.locale.fr.formats
Check import: django.conf.locale.fy
Check import: django.conf.locale.fy.formats
Check import: django.conf.locale.ga
Check import: django.conf.locale.ga.formats
Check import: django.conf.locale.gd
Check import: django.conf.locale.gd.formats
Check import: django.conf.locale.gl
Check import: django.conf.locale.gl.formats
Check import: django.conf.locale.he
Check import: django.conf.locale.he.formats
Check import: django.conf.locale.hi
Check import: django.conf.locale.hi.formats
Check import: django.conf.locale.hr
Check import: django.conf.locale.hr.formats
Check import: django.conf.locale.hu
Check import: django.conf.locale.hu.formats
Check import: django.conf.locale.id
Check import: django.conf.locale.id.formats
Check import: django.conf.locale.ig
Check import: django.conf.locale.ig.formats
Check import: django.conf.locale.it
Check import: django.conf.locale.it.formats
Check import: django.conf.locale.ja
Check import: django.conf.locale.ja.formats
Check import: django.conf.locale.ka
Check import: django.conf.locale.ka.formats
Check import: django.conf.locale.km
Check import: django.conf.locale.km.formats
Check import: django.conf.locale.kn
Check import: django.conf.locale.kn.formats
Check import: django.conf.locale.ko
Check import: django.conf.locale.ko.formats
Check import: django.conf.locale.ky
Check import: django.conf.locale.ky.formats
Check import: django.conf.locale.lt
Check import: django.conf.locale.lt.formats
Check import: django.conf.locale.lv
Check import: django.conf.locale.lv.formats
Check import: django.conf.locale.mk
Check import: django.conf.locale.mk.formats
Check import: django.conf.locale.ml
Check import: django.conf.locale.ml.formats
Check import: django.conf.locale.mn
Check import: django.conf.locale.mn.formats
Check import: django.conf.locale.ms
Check import: django.conf.locale.ms.formats
Check import: django.conf.locale.nb
Check import: django.conf.locale.nb.formats
Check import: django.conf.locale.nl
Check import: django.conf.locale.nl.formats
Check import: django.conf.locale.nn
Check import: django.conf.locale.nn.formats
Check import: django.conf.locale.pl
Check import: django.conf.locale.pl.formats
Check import: django.conf.locale.pt
Check import: django.conf.locale.pt.formats
Check import: django.conf.locale.pt_BR
Check import: django.conf.locale.pt_BR.formats
Check import: django.conf.locale.ro
Check import: django.conf.locale.ro.formats
Check import: django.conf.locale.ru
Check import: django.conf.locale.ru.formats
Check import: django.conf.locale.sk
Check import: django.conf.locale.sk.formats
Check import: django.conf.locale.sl
Check import: django.conf.locale.sl.formats
Check import: django.conf.locale.sq
Check import: django.conf.locale.sq.formats
Check import: django.conf.locale.sr
Check import: django.conf.locale.sr.formats
Check import: django.conf.locale.sr_Latn
Check import: django.conf.locale.sr_Latn.formats
Check import: django.conf.locale.sv
Check import: django.conf.locale.sv.formats
Check import: django.conf.locale.ta
Check import: django.conf.locale.ta.formats
Check import: django.conf.locale.te
Check import: django.conf.locale.te.formats
Check import: django.conf.locale.tg
Check import: django.conf.locale.tg.formats
Check import: django.conf.locale.th
Check import: django.conf.locale.th.formats
Check import: django.conf.locale.tk
Check import: django.conf.locale.tk.formats
Check import: django.conf.locale.tr
Check import: django.conf.locale.tr.formats
Check import: django.conf.locale.uk
Check import: django.conf.locale.uk.formats
Check import: django.conf.locale.uz
Check import: django.conf.locale.uz.formats
Check import: django.conf.locale.vi
Check import: django.conf.locale.vi.formats
Check import: django.conf.locale.zh_Hans
Check import: django.conf.locale.zh_Hans.formats
Check import: django.conf.locale.zh_Hant
Check import: django.conf.locale.zh_Hant.formats
Check import: django.conf.urls
Check import: django.conf.urls.i18n
Check import: django.conf.urls.static
Check import: django.contrib
Check import: django.core
Check import: django.core.asgi
Check import: django.core.cache
Check import: django.core.cache.backends
Check import: django.core.cache.backends.base
Check import: django.core.cache.backends.db
Check import: django.core.cache.backends.dummy
Check import: django.core.cache.backends.filebased
Check import: django.core.cache.backends.locmem
Check import: django.core.cache.backends.memcached
Check import: django.core.cache.backends.redis
Check import: django.core.cache.utils
Check import: django.core.checks
Check import: django.core.checks.async_checks
Check import: django.core.checks.caches
Check import: django.core.checks.compatibility
Check import: django.core.checks.compatibility.django_4_0
Check import: django.core.checks.database
Check import: django.core.checks.files
Check import: django.core.checks.messages
Check import: django.core.checks.model_checks
Check import: django.core.checks.registry
Check import: django.core.checks.security
Check import: django.core.checks.security.base
Check import: django.core.checks.security.csrf
Check import: django.core.checks.security.sessions
Check import: django.core.checks.templates
Check import: django.core.checks.translation
Check import: django.core.checks.urls
Check import: django.core.exceptions
Check import: django.core.files
Check import: django.core.files.base
Check import: django.core.files.images
Check import: django.core.files.locks
Check import: django.core.files.move
Check import: django.core.files.storage
Check import: django.core.files.storage.base
Check import: django.core.files.storage.filesystem
Check import: django.core.files.storage.handler
Check import: django.core.files.storage.memory
Check import: django.core.files.storage.mixins
Check import: django.core.files.temp
Check import: django.core.files.uploadedfile
Check import: django.core.files.uploadhandler
Check import: django.core.files.utils
Check import: django.core.handlers
Check import: django.core.handlers.asgi
Check import: django.core.handlers.base
Check import: django.core.handlers.exception
Check import: django.core.handlers.wsgi
Check import: django.core.mail
Check import: django.core.mail.backends
Check import: django.core.mail.backends.base
Check import: django.core.mail.backends.console
Check import: django.core.mail.backends.dummy
Check import: django.core.mail.backends.filebased
Check import: django.core.mail.backends.locmem
Check import: django.core.mail.backends.smtp
Check import: django.core.mail.message
Check import: django.core.mail.utils
Check import: django.core.management
Check import: django.core.management.base
Check import: django.core.management.color
Check import: django.core.management.commands
Check import: django.core.management.commands.check
Check import: django.core.management.commands.compilemessages
Check import: django.core.management.commands.createcachetable
Check import: django.core.management.commands.dbshell
Check import: django.core.management.commands.diffsettings
Check import: django.core.management.commands.dumpdata
Check import: django.core.management.commands.flush
Check import: django.core.management.commands.inspectdb
Check import: django.core.management.commands.loaddata
Check import: django.core.management.commands.makemessages
Check import: django.core.management.commands.makemigrations
Check import: django.core.management.commands.migrate
Check import: django.core.management.commands.optimizemigration
Check import: django.core.management.commands.runserver
Check import: django.core.management.commands.sendtestemail
Check import: django.core.management.commands.shell
Check import: django.core.management.commands.showmigrations
Check import: django.core.management.commands.sqlflush
Check import: django.core.management.commands.sqlmigrate
Check import: django.core.management.commands.sqlsequencereset
Check import: django.core.management.commands.squashmigrations
Check import: django.core.management.commands.startapp
Check import: django.core.management.commands.startproject
Check import: django.core.management.commands.test
Check import: django.core.management.commands.testserver
Check import: django.core.management.sql
Check import: django.core.management.templates
Check import: django.core.management.utils
Check import: django.core.paginator
Check import: django.core.serializers
Check import: django.core.serializers.base
Check import: django.core.serializers.json
Check import: django.core.serializers.jsonl
Check import: django.core.serializers.python
Check import: django.core.serializers.xml_serializer
Check import: django.core.servers
Check import: django.core.servers.basehttp
Check import: django.core.signals
Check import: django.core.signing
Check import: django.core.validators
Check import: django.core.wsgi
Check import: django.db
Check import: django.db.backends
Check import: django.db.backends.base
Check import: django.db.backends.base.base
Check import: django.db.backends.base.client
Check import: django.db.backends.base.creation
Check import: django.db.backends.base.features
Check import: django.db.backends.base.introspection
Check import: django.db.backends.base.operations
Check import: django.db.backends.base.schema
Check import: django.db.backends.base.validation
Check import: django.db.backends.ddl_references
Check import: django.db.backends.dummy
Check import: django.db.backends.dummy.base
Check import: django.db.backends.dummy.features
Check import: django.db.backends.signals
Check import: django.db.backends.sqlite3
Check import: django.db.backends.sqlite3.base
Check import: django.db.backends.sqlite3.client
Check import: django.db.backends.sqlite3.creation
Check import: django.db.backends.sqlite3.features
Check import: django.db.backends.sqlite3.introspection
Check import: django.db.backends.sqlite3.operations
Check import: django.db.backends.sqlite3.schema
Check import: django.db.backends.utils
Check import: django.db.migrations
Check import: django.db.migrations.autodetector
Check import: django.db.migrations.exceptions
Check import: django.db.migrations.executor
Check import: django.db.migrations.graph
Check import: django.db.migrations.loader
Check import: django.db.migrations.migration
Check import: django.db.migrations.operations
Check import: django.db.migrations.operations.base
Check import: django.db.migrations.operations.fields
Check import: django.db.migrations.operations.models
Check import: django.db.migrations.operations.special
Check import: django.db.migrations.optimizer
Check import: django.db.migrations.questioner
Check import: django.db.migrations.recorder
Check import: django.db.migrations.serializer
Check import: django.db.migrations.state
Check import: django.db.migrations.utils
Check import: django.db.migrations.writer
Check import: django.db.models
Check import: django.db.models.aggregates
Check import: django.db.models.base
Check import: django.db.models.constants
Check import: django.db.models.constraints
Check import: django.db.models.deletion
Check import: django.db.models.enums
Check import: django.db.models.expressions
Check import: django.db.models.fields
Check import: django.db.models.fields.files
Check import: django.db.models.fields.json
Check import: django.db.models.fields.mixins
Check import: django.db.models.fields.proxy
Check import: django.db.models.fields.related
Check import: django.db.models.fields.related_descriptors
Check import: django.db.models.fields.related_lookups
Check import: django.db.models.fields.reverse_related
Check import: django.db.models.functions
Check import: django.db.models.functions.comparison
Check import: django.db.models.functions.datetime
Check import: django.db.models.functions.math
Check import: django.db.models.functions.mixins
Check import: django.db.models.functions.text
Check import: django.db.models.functions.window
Check import: django.db.models.indexes
Check import: django.db.models.lookups
Check import: django.db.models.manager
Check import: django.db.models.options
Check import: django.db.models.query
Check import: django.db.models.query_utils
Check import: django.db.models.signals
Check import: django.db.models.sql
Check import: django.db.models.sql.compiler
Check import: django.db.models.sql.constants
Check import: django.db.models.sql.datastructures
Check import: django.db.models.sql.query
Check import: django.db.models.sql.subqueries
Check import: django.db.models.sql.where
Check import: django.db.models.utils
Check import: django.db.transaction
Check import: django.db.utils
Check import: django.dispatch
Check import: django.dispatch.dispatcher
Check import: django.forms
Check import: django.forms.boundfield
Check import: django.forms.fields
Check import: django.forms.forms
Check import: django.forms.formsets
Check import: django.forms.models
Check import: django.forms.renderers
Check import: django.forms.utils
Check import: django.forms.widgets
Check import: django.http
Check import: django.http.cookie
Check import: django.http.multipartparser
Check import: django.http.request
Check import: django.http.response
Check import: django.middleware
Check import: django.middleware.cache
Check import: django.middleware.clickjacking
Check import: django.middleware.common
Check import: django.middleware.csrf
Check import: django.middleware.gzip
Check import: django.middleware.http
Check import: django.middleware.locale
Check import: django.middleware.security
Check import: django.shortcuts
Check import: django.template
Check import: django.template.autoreload
Check import: django.template.backends
Check import: django.template.backends.base
Check import: django.template.backends.django
Check import: django.template.backends.dummy
Check import: django.template.backends.jinja2
Check import: django.template.backends.utils
Check import: django.template.base
Check import: django.template.context
Check import: django.template.context_processors
Check import: django.template.defaultfilters
Check import: django.template.defaulttags
Check import: django.template.engine
Check import: django.template.exceptions
Check import: django.template.library
Check import: django.template.loader
Check import: django.template.loader_tags
Check import: django.template.loaders
Check import: django.template.loaders.app_directories
Check import: django.template.loaders.base
Check import: django.template.loaders.cached
Check import: django.template.loaders.filesystem
Check import: django.template.loaders.locmem
Check import: django.template.response
Check import: django.template.smartif
Check import: django.template.utils
Check import: django.templatetags
Check import: django.templatetags.cache
Check import: django.templatetags.i18n
Check import: django.templatetags.l10n
Check import: django.templatetags.static
Check import: django.templatetags.tz
Check import: django.test
Check import: django.test.client
Check import: django.test.html
Check import: django.test.runner
Check import: django.test.selenium
Check import: django.test.signals
Check import: django.test.testcases
Check import: django.test.utils
Check import: django.urls
Check import: django.urls.base
Check import: django.urls.conf
Check import: django.urls.converters
Check import: django.urls.exceptions
Check import: django.urls.resolvers
Check import: django.urls.utils
Check import: django.utils
Check import: django.utils.archive
Check import: django.utils.asyncio
Check import: django.utils.autoreload
Check import: django.utils.baseconv
Check import: django.utils.cache
Check import: django.utils.connection
Check import: django.utils.crypto
Check import: django.utils.datastructures
Check import: django.utils.dateformat
Check import: django.utils.dateparse
Check import: django.utils.dates
Check import: django.utils.datetime_safe
Check import: django.utils.deconstruct
Check import: django.utils.decorators
Check import: django.utils.deprecation
Check import: django.utils.duration
Check import: django.utils.encoding
Check import: django.utils.feedgenerator
Check import: django.utils.formats
Check import: django.utils.functional
Check import: django.utils.hashable
Check import: django.utils.html
Check import: django.utils.http
Check import: django.utils.inspect
Check import: django.utils.ipv6
Check import: django.utils.itercompat
Check import: django.utils.jslex
Check import: django.utils.log
Check import: django.utils.lorem_ipsum
Check import: django.utils.module_loading
Check import: django.utils.numberformat
Check import: django.utils.regex_helper
Check import: django.utils.safestring
Check import: django.utils.termcolors
Check import: django.utils.text
Check import: django.utils.timesince
Check import: django.utils.timezone
Check import: django.utils.topological_sort
Check import: django.utils.translation
Check import: django.utils.translation.reloader
Check import: django.utils.translation.template
Check import: django.utils.translation.trans_null
Check import: django.utils.translation.trans_real
Check import: django.utils.tree
Check import: django.utils.version
Check import: django.utils.xmlutils
Check import: django.views
Check import: django.views.csrf
Check import: django.views.debug
Check import: django.views.decorators
Check import: django.views.decorators.cache
Check import: django.views.decorators.clickjacking
Check import: django.views.decorators.common
Check import: django.views.decorators.csrf
Check import: django.views.decorators.debug
Check import: django.views.decorators.gzip
Check import: django.views.decorators.http
Check import: django.views.decorators.vary
Check import: django.views.defaults
Check import: django.views.generic
Check import: django.views.generic.base
Check import: django.views.generic.dates
Check import: django.views.generic.detail
Check import: django.views.generic.edit
Check import: django.views.generic.list
Check import: django.views.i18n
Check import: django.views.static
+ RPM_EC=0
++ jobs -p
+ exit 0
Processing files: python-django4.2-bash-completion-4.2.20-2.fc43.noarch
Provides: python-django-bash-completion-impl python-django4.2-bash-completion = 4.2.20-2.fc43
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Conflicts: python-django-bash-completion-impl
Processing files: python3-django4.2-doc-4.2.20-2.fc43.noarch
Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.bvlYbk
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ LICENSEDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/licenses/python3-django4.2-doc
+ export LC_ALL=C.UTF-8
+ LC_ALL=C.UTF-8
+ export LICENSEDIR
+ /usr/bin/mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/licenses/python3-django4.2-doc
+ cp -pr /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/LICENSE /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/licenses/python3-django4.2-doc
+ RPM_EC=0
++ jobs -p
+ exit 0
warning: File listed twice: /usr/share/doc/python3-django4.2-doc/_static/fontawesome/LICENSE.txt
Provides: python-django-doc-impl python-django4.2-doc = 4.2.20-2.fc43 python3-django4.2-doc = 4.2.20-2.fc43 python3.13-django4.2-doc = 4.2.20-2.fc43
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Conflicts: python-django-doc-impl
Suggests: python3-django4.2 = 4.2.20-2.fc43
Processing files: python3-django4.2-4.2.20-2.fc43.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.0kojZ9
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ cd Django-4.2.20
+ DOCDIR=/builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/doc/python3-django4.2
+ export LC_ALL=C.UTF-8
+ LC_ALL=C.UTF-8
+ export DOCDIR
+ /usr/bin/mkdir -p /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/doc/python3-django4.2
+ cp -pr /builddir/build/BUILD/python-django4.2-4.2.20-build/Django-4.2.20/README.rst /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT/usr/share/doc/python3-django4.2
+ RPM_EC=0
++ jobs -p
+ exit 0
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/img/LICENSE
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/img/README.txt
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/gis/gdal/LICENSE
warning: File listed twice: /usr/lib/python3.13/site-packages/django/contrib/gis/geos/LICENSE
Provides: bundled(jquery) = 3.6.4 bundled(select2) = 4.0.13 bundled(xregexp) = 3.2.0 python-django-impl python-django4.2 = 4.2.20-2.fc43 python3-django4.2 = 4.2.20-2.fc43 python3.13-django4.2 = 4.2.20-2.fc43 python3.13dist(django) = 4.2.20 python3dist(django) = 4.2.20
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.13dist(asgiref) < 4~~ with python3.13dist(asgiref) >= 3.6) /usr/bin/python3 python(abi) = 3.13 python3.13dist(sqlparse) >= 0.3.1
Conflicts: python-django-impl
Recommends: (python-django4.2-bash-completion = 4.2.20-2.fc43 if bash-completion)
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILD/python-django4.2-4.2.20-build/BUILDROOT
Wrote: /builddir/build/SRPMS/python-django4.2-4.2.20-2.fc43.src.rpm
Wrote: /builddir/build/RPMS/python-django4.2-bash-completion-4.2.20-2.fc43.noarch.rpm
Wrote: /builddir/build/RPMS/python3-django4.2-4.2.20-2.fc43.noarch.rpm
Wrote: /builddir/build/RPMS/python3-django4.2-doc-4.2.20-2.fc43.noarch.rpm
Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.LvTKPA
+ umask 022
+ cd /builddir/build/BUILD/python-django4.2-4.2.20-build
+ test -d /builddir/build/BUILD/python-django4.2-4.2.20-build
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /builddir/build/BUILD/python-django4.2-4.2.20-build
+ rm -rf /builddir/build/BUILD/python-django4.2-4.2.20-build
+ RPM_EC=0
++ jobs -p
+ exit 0

RPM build warnings:
    File listed twice: /usr/share/doc/python3-django4.2-doc/_static/fontawesome/LICENSE.txt
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/img/LICENSE
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/img/README.txt
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/gis/gdal/LICENSE
    File listed twice: /usr/lib/python3.13/site-packages/django/contrib/gis/geos/LICENSE
Finish: rpmbuild python-django4.2-4.2.20-2.fc43.src.rpm
Finish: build phase for python-django4.2-4.2.20-2.fc43.src.rpm
INFO: chroot_scan: 1 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-rawhide-x86_64-1748943842.640973/root/var/log/dnf5.log
INFO: chroot_scan: creating tarball /var/lib/copr-rpmbuild/results/chroot_scan.tar.gz
/bin/tar: Removing leading `/' from member names
INFO: Done(/var/lib/copr-rpmbuild/results/python-django4.2-4.2.20-2.fc43.src.rpm) Config(child) 2 minutes 16 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
Finish: run
Running RPMResults tool
Package info:
{
    "packages": [
        {
            "name": "python-django4.2-bash-completion",
            "epoch": null,
            "version": "4.2.20",
            "release": "2.fc43",
            "arch": "noarch"
        },
        {
            "name": "python3-django4.2-doc",
            "epoch": null,
            "version": "4.2.20",
            "release": "2.fc43",
            "arch": "noarch"
        },
        {
            "name": "python-django4.2",
            "epoch": null,
            "version": "4.2.20",
            "release": "2.fc43",
            "arch": "src"
        },
        {
            "name": "python3-django4.2",
            "epoch": null,
            "version": "4.2.20",
            "release": "2.fc43",
            "arch": "noarch"
        }
    ]
}
RPMResults finished