Warning: Permanently added '44.200.172.91' (ED25519) to the list of known hosts. You can reproduce this build on your computer by running: sudo dnf install copr-rpmbuild /usr/bin/copr-rpmbuild --verbose --drop-resultdir --task-url https://copr.fedorainfracloud.org/backend/get-build-task/6683726-fedora-rawhide-x86_64 --chroot fedora-rawhide-x86_64 Version: 0.69 PID: 21867 Logging PID: 21868 Task: {'appstream': False, 'background': False, 'build_id': 6683726, 'buildroot_pkgs': [], 'chroot': 'fedora-rawhide-x86_64', 'enable_net': False, 'fedora_review': False, 'git_hash': '588e2f21c71c86d1459ab9bd190fd780f455af7a', 'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/thrnciar/python-requests-5b54aca4/python-django-mailman3', 'isolation': 'default', 'memory_reqs': 2048, 'package_name': 'python-django-mailman3', 'package_version': '1.3.9-1', 'project_dirname': 'python-requests-5b54aca4', 'project_name': 'python-requests-5b54aca4', 'project_owner': 'thrnciar', 'repo_priority': None, 'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/thrnciar/python-requests-5b54aca4/fedora-rawhide-x86_64/', 'id': 'copr_base', 'name': 'Copr repository', 'priority': None}], 'sandbox': 'thrnciar/python-requests-5b54aca4--thrnciar', 'source_json': {}, 'source_type': None, 'submitter': 'thrnciar', 'tags': [], 'task_id': '6683726-fedora-rawhide-x86_64', 'timeout': 18000, 'uses_devel_repo': False, 'with_opts': [], 'without_opts': []} Running: git clone https://copr-dist-git.fedorainfracloud.org/git/thrnciar/python-requests-5b54aca4/python-django-mailman3 /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3 --depth 500 --no-single-branch --recursive cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/thrnciar/python-requests-5b54aca4/python-django-mailman3', '/var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3', '--depth', '500', '--no-single-branch', '--recursive'] cwd: . rc: 0 stdout: stderr: Cloning into '/var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3'... Running: git checkout 588e2f21c71c86d1459ab9bd190fd780f455af7a -- cmd: ['git', 'checkout', '588e2f21c71c86d1459ab9bd190fd780f455af7a', '--'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3 rc: 0 stdout: stderr: Note: switching to '588e2f21c71c86d1459ab9bd190fd780f455af7a'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false HEAD is now at 588e2f2 automatic import of python-django-mailman3 Running: copr-distgit-client sources cmd: ['copr-distgit-client', 'sources'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3 rc: 0 stdout: stderr: INFO: Reading stdout from command: git rev-parse --abbrev-ref HEAD INFO: Reading stdout from command: git rev-parse HEAD INFO: Reading sources specification file: sources INFO: Downloading django-mailman3-1.3.9.tar.gz INFO: Reading stdout from command: curl --help all /usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated INFO: Calling: curl -H Pragma: -o django-mailman3-1.3.9.tar.gz --location --connect-timeout 60 --retry 3 --retry-delay 10 --remote-time --show-error --fail --retry-all-errors https://copr-dist-git.fedorainfracloud.org/repo/pkgs/thrnciar/python-requests-5b54aca4/python-django-mailman3/django-mailman3-1.3.9.tar.gz/md5/f55c3639d3bf7757726080ca23111653/django-mailman3-1.3.9.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 402k 100 402k 0 0 2514k 0 --:--:-- --:--:-- --:--:-- 2517k INFO: Reading stdout from command: md5sum django-mailman3-1.3.9.tar.gz Running (timeout=18000): unbuffer mock --spec /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3/python-django-mailman3.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3 --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1700753703.420278 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 5.2 starting (python version = 3.11.3, NVR = mock-5.2-1.fc38), args: /usr/libexec/mock/mock --spec /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3/python-django-mailman3.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3 --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1700753703.420278 -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-pknhjbqd/python-django-mailman3/python-django-mailman3.spec) Config(fedora-rawhide-x86_64) Start: clean chroot Finish: clean chroot Mock Version: 5.2 INFO: Mock Version: 5.2 Start(bootstrap): chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1700753703.420278/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 bootstrap image: registry.fedoraproject.org/fedora:rawhide INFO: Pulling image: registry.fedoraproject.org/fedora:rawhide INFO: Copy content of container registry.fedoraproject.org/fedora:rawhide to /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1700753703.420278/root INFO: Checking that registry.fedoraproject.org/fedora:rawhide image matches host's architecture INFO: mounting registry.fedoraproject.org/fedora:rawhide with podman image mount INFO: image registry.fedoraproject.org/fedora:rawhide as /var/lib/containers/storage/overlay/2867afab974f7855400f2f3efe60e26946dde0e813e737eaca38ba651d113485/merged INFO: umounting image registry.fedoraproject.org/fedora:rawhide (/var/lib/containers/storage/overlay/2867afab974f7855400f2f3efe60e26946dde0e813e737eaca38ba651d113485/merged) with podman image umount INFO: Package manager dnf detected and used (fallback) INFO: Bootstrap image not marked ready Start(bootstrap): installing dnf tooling No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 80 MB/s | 3.5 MB 00:00 fedora 67 MB/s | 72 MB 00:01 Last metadata expiration check: 0:00:01 ago on Thu Nov 23 15:35:06 2023. Package python3-dnf-4.18.1-2.fc40.noarch is already installed. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: python3-dnf-plugins-core noarch 4.4.3-1.fc40 copr_base 302 k Installing dependencies: dbus-libs x86_64 1:1.14.10-1.fc40 fedora 155 k python3-dateutil noarch 1:2.8.2-11.fc40 copr_base 345 k python3-dbus x86_64 1.3.2-4.fc39 fedora 157 k python3-distro noarch 1.8.0-6.fc39 fedora 49 k python3-six noarch 1.16.0-12.fc39 fedora 41 k python3-systemd x86_64 235-5.fc39 fedora 107 k Transaction Summary ================================================================================ Install 7 Packages Total download size: 1.1 M Installed size: 3.6 M Downloading Packages: (1/7): python3-dnf-plugins-core-4.4.3-1.fc40.no 21 MB/s | 302 kB 00:00 (2/7): python3-dateutil-2.8.2-11.fc40.noarch.rp 18 MB/s | 345 kB 00:00 (3/7): python3-distro-1.8.0-6.fc39.noarch.rpm 120 kB/s | 49 kB 00:00 (4/7): python3-six-1.16.0-12.fc39.noarch.rpm 456 kB/s | 41 kB 00:00 (5/7): dbus-libs-1.14.10-1.fc40.x86_64.rpm 258 kB/s | 155 kB 00:00 (6/7): python3-dbus-1.3.2-4.fc39.x86_64.rpm 260 kB/s | 157 kB 00:00 (7/7): python3-systemd-235-5.fc39.x86_64.rpm 589 kB/s | 107 kB 00:00 -------------------------------------------------------------------------------- Total 1.5 MB/s | 1.1 MB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python3-systemd-235-5.fc39.x86_64 1/7 Installing : python3-six-1.16.0-12.fc39.noarch 2/7 Installing : python3-dateutil-1:2.8.2-11.fc40.noarch 3/7 Installing : python3-distro-1.8.0-6.fc39.noarch 4/7 Installing : dbus-libs-1:1.14.10-1.fc40.x86_64 5/7 Installing : python3-dbus-1.3.2-4.fc39.x86_64 6/7 Installing : python3-dnf-plugins-core-4.4.3-1.fc40.noarch 7/7 Running scriptlet: python3-dnf-plugins-core-4.4.3-1.fc40.noarch 7/7 Installed: dbus-libs-1:1.14.10-1.fc40.x86_64 python3-dateutil-1:2.8.2-11.fc40.noarch python3-dbus-1.3.2-4.fc39.x86_64 python3-distro-1.8.0-6.fc39.noarch python3-dnf-plugins-core-4.4.3-1.fc40.noarch python3-six-1.16.0-12.fc39.noarch python3-systemd-235-5.fc39.x86_64 Complete! Finish(bootstrap): installing dnf tooling 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-1700753703.420278/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 dnf detected and used (direct choice) Start: installing minimal buildroot with dnf No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 87 kB/s | 1.5 kB 00:00 Copr repository 53 MB/s | 3.5 MB 00:00 fedora 311 kB/s | 20 kB 00:00 Dependencies resolved. ================================================================================ Package Arch Version Repo Size ================================================================================ Installing group/module packages: bash x86_64 5.2.21-2.fc40 fedora 1.8 M bzip2 x86_64 1.0.8-16.fc39 fedora 52 k coreutils x86_64 9.4-1.fc40 fedora 1.1 M cpio x86_64 2.14-5.fc40 fedora 280 k diffutils x86_64 3.10-3.fc39 fedora 398 k fedora-release-common noarch 40-0.20 fedora 20 k findutils x86_64 1:4.9.0-6.fc40 fedora 492 k gawk x86_64 5.2.2-2.fc39 fedora 1.1 M glibc-minimal-langpack x86_64 2.38.9000-22.fc40 fedora 81 k grep x86_64 3.11-5.fc40 fedora 298 k gzip x86_64 1.12-6.fc39 fedora 166 k info x86_64 7.1-1.fc40 fedora 184 k patch x86_64 2.7.6-22.fc39 fedora 125 k redhat-rpm-config noarch 271-1.fc40 fedora 81 k rpm-build x86_64 4.19.0-2.fc40 fedora 79 k sed x86_64 4.8-14.fc39 fedora 306 k shadow-utils x86_64 2:4.14.0-2.fc40 fedora 1.3 M tar x86_64 2:1.35-2.fc40 fedora 864 k unzip x86_64 6.0-62.fc39 fedora 184 k util-linux x86_64 2.39.2-1.fc40 fedora 1.2 M which x86_64 2.21-40.fc39 fedora 42 k xz x86_64 5.4.5-1.fc40 fedora 557 k Installing dependencies: alternatives x86_64 1.25-1.fc39 fedora 39 k ansible-srpm-macros noarch 1-11.fc39 fedora 21 k audit-libs x86_64 3.1.2-5.fc40 fedora 117 k authselect x86_64 1.4.3-1.fc40 fedora 149 k authselect-libs x86_64 1.4.3-1.fc40 fedora 249 k basesystem noarch 11-18.fc39 fedora 7.2 k binutils x86_64 2.41-14.fc40 fedora 6.3 M binutils-gold x86_64 2.41-14.fc40 fedora 797 k bzip2-libs x86_64 1.0.8-16.fc39 fedora 41 k ca-certificates noarch 2023.2.62_v7.0.401-4.fc40 fedora 863 k coreutils-common x86_64 9.4-1.fc40 fedora 2.1 M cracklib x86_64 2.9.11-2.fc39 fedora 94 k crypto-policies noarch 20231113-1.gitb402e82.fc40 fedora 99 k curl x86_64 8.4.0-1.fc40 fedora 362 k cyrus-sasl-lib x86_64 2.1.28-11.fc39 fedora 793 k debugedit x86_64 5.0-11.fc40 fedora 77 k dwz x86_64 0.15-3.fc39 fedora 134 k ed x86_64 1.19-4.fc39 fedora 79 k efi-srpm-macros noarch 5-9.fc39 fedora 22 k elfutils x86_64 0.190-2.fc40 fedora 551 k elfutils-debuginfod-client x86_64 0.190-2.fc40 fedora 39 k elfutils-default-yama-scope noarch 0.190-2.fc40 fedora 14 k elfutils-libelf x86_64 0.190-2.fc40 fedora 195 k elfutils-libs x86_64 0.190-2.fc40 fedora 260 k fedora-gpg-keys noarch 40-0.2 fedora 130 k fedora-release noarch 40-0.20 fedora 9.3 k fedora-release-identity-basic noarch 40-0.20 fedora 10 k fedora-repos noarch 40-0.2 fedora 9.3 k fedora-repos-rawhide noarch 40-0.2 fedora 8.9 k file x86_64 5.45-1.fc40 fedora 49 k file-libs x86_64 5.45-1.fc40 fedora 763 k filesystem x86_64 3.18-6.fc39 fedora 1.1 M fonts-srpm-macros noarch 1:2.0.5-12.fc39 fedora 26 k forge-srpm-macros noarch 0.1.0-1.fc40 fedora 18 k fpc-srpm-macros noarch 1.3-8.fc39 fedora 7.4 k gdb-minimal x86_64 13.2-11.fc40 fedora 4.2 M gdbm x86_64 1:1.23-4.fc39 fedora 155 k gdbm-libs x86_64 1:1.23-4.fc39 fedora 56 k ghc-srpm-macros noarch 1.6.1-3.fc40 fedora 8.1 k glibc x86_64 2.38.9000-22.fc40 fedora 2.2 M glibc-common x86_64 2.38.9000-22.fc40 fedora 363 k glibc-gconv-extra x86_64 2.38.9000-22.fc40 fedora 1.7 M gmp x86_64 1:6.2.1-5.fc39 fedora 313 k gnat-srpm-macros noarch 6-3.fc39 fedora 8.8 k go-srpm-macros noarch 3.3.1-1.fc40 fedora 28 k jansson x86_64 2.13.1-7.fc40 copr_base 45 k kernel-srpm-macros noarch 1.0-20.fc39 fedora 10 k keyutils-libs x86_64 1.6.1-7.fc39 fedora 31 k krb5-libs x86_64 1.21.2-2.fc40 copr_base 761 k libacl x86_64 2.3.1-10.fc40 fedora 23 k libarchive x86_64 3.7.2-1.fc40 fedora 408 k libattr x86_64 2.5.1-9.fc40 fedora 18 k libblkid x86_64 2.39.2-1.fc40 fedora 116 k libbrotli x86_64 1.1.0-1.fc40 fedora 336 k libcap x86_64 2.69-1.fc40 fedora 83 k libcap-ng x86_64 0.8.3-8.fc40 fedora 32 k libcom_err x86_64 1.47.0-2.fc39 fedora 26 k libcurl x86_64 8.4.0-1.fc40 fedora 343 k libeconf x86_64 0.5.2-1.fc40 fedora 30 k libevent x86_64 2.1.12-9.fc39 fedora 258 k libfdisk x86_64 2.39.2-1.fc40 fedora 162 k libffi x86_64 3.4.4-4.fc39 fedora 40 k libgcc x86_64 13.2.1-5.fc40 fedora 112 k libgomp x86_64 13.2.1-5.fc40 fedora 321 k libidn2 x86_64 2.3.4-3.fc39 fedora 117 k libmount x86_64 2.39.2-1.fc40 fedora 154 k libnghttp2 x86_64 1.58.0-1.fc40 fedora 76 k libnsl2 x86_64 2.0.0-6.fc39 fedora 30 k libpkgconf x86_64 1.9.5-2.fc39 fedora 38 k libpsl x86_64 0.21.2-4.fc39 fedora 63 k libpwquality x86_64 1.4.5-6.fc39 fedora 120 k libselinux x86_64 3.6-0.rc1.1.fc40 fedora 87 k libsemanage x86_64 3.6-0.rc1.1.fc40 fedora 116 k libsepol x86_64 3.6-0.rc1.1.fc40 fedora 340 k libsigsegv x86_64 2.14-5.fc39 fedora 27 k libsmartcols x86_64 2.39.2-1.fc40 fedora 67 k libssh x86_64 0.10.5-2.fc39 fedora 211 k libssh-config noarch 0.10.5-2.fc39 fedora 9.2 k libstdc++ x86_64 13.2.1-5.fc40 fedora 864 k libtasn1 x86_64 4.19.0-3.fc39 fedora 74 k libtirpc x86_64 1.3.4-0.fc40 fedora 94 k libunistring x86_64 1.1-5.fc40 fedora 543 k libutempter x86_64 1.2.1-10.fc39 fedora 26 k libuuid x86_64 2.39.2-1.fc40 fedora 28 k libverto x86_64 0.3.2-6.fc39 fedora 20 k libxcrypt x86_64 4.4.36-2.fc39 fedora 119 k libxml2 x86_64 2.12.0-1.fc40 fedora 698 k libzstd x86_64 1.5.5-4.fc39 fedora 309 k lua-libs x86_64 5.4.6-3.fc39 fedora 133 k lua-srpm-macros noarch 1-9.fc39 fedora 8.6 k lz4-libs x86_64 1.9.4-4.fc39 fedora 67 k mpfr x86_64 4.2.1-1.fc40 fedora 343 k ncurses-base noarch 6.4-8.20231001.fc40 fedora 88 k ncurses-libs x86_64 6.4-8.20231001.fc40 fedora 338 k ocaml-srpm-macros noarch 9-1.fc40 fedora 9.0 k openblas-srpm-macros noarch 2-14.fc39 fedora 7.5 k openldap x86_64 2.6.6-1.fc39 fedora 255 k openssl-libs x86_64 1:3.1.4-1.fc40 fedora 2.2 M p11-kit x86_64 0.25.3-1.fc40 fedora 522 k p11-kit-trust x86_64 0.25.3-1.fc40 fedora 142 k package-notes-srpm-macros noarch 0.5-9.fc39 fedora 11 k pam x86_64 1.5.3-8.fc40 fedora 547 k pam-libs x86_64 1.5.3-8.fc40 fedora 57 k pcre2 x86_64 10.42-2.fc40 fedora 233 k pcre2-syntax noarch 10.42-2.fc40 fedora 143 k perl-srpm-macros noarch 1-51.fc39 fedora 8.0 k pkgconf x86_64 1.9.5-2.fc39 fedora 42 k pkgconf-m4 noarch 1.9.5-2.fc39 fedora 14 k pkgconf-pkg-config x86_64 1.9.5-2.fc39 fedora 9.6 k popt x86_64 1.19-3.fc39 fedora 66 k publicsuffix-list-dafsa noarch 20230812-1.fc40 fedora 57 k pyproject-srpm-macros noarch 1.10.0-1.fc40 fedora 14 k python-srpm-macros noarch 3.12-4.fc40 fedora 25 k qt5-srpm-macros noarch 5.15.11-1.fc40 fedora 8.3 k qt6-srpm-macros noarch 6.6.0-1.fc40 fedora 8.7 k readline x86_64 8.2-4.fc39 fedora 213 k rpm x86_64 4.19.0-2.fc40 fedora 538 k rpm-build-libs x86_64 4.19.0-2.fc40 fedora 96 k rpm-libs x86_64 4.19.0-2.fc40 fedora 312 k rpm-sequoia x86_64 1.5.0-1.fc40 fedora 883 k rust-srpm-macros noarch 25.2-2.fc40 fedora 13 k setup noarch 2.14.4-1.fc39 fedora 154 k sqlite-libs x86_64 3.44.0-1.fc40 fedora 692 k systemd-libs x86_64 255~rc3-1.fc40 fedora 702 k util-linux-core x86_64 2.39.2-1.fc40 fedora 493 k xxhash-libs x86_64 0.8.2-1.fc39 fedora 37 k xz-libs x86_64 5.4.5-1.fc40 fedora 108 k zip x86_64 3.0-39.fc40 fedora 266 k zlib x86_64 1.2.13-5.fc40 fedora 94 k zstd x86_64 1.5.5-4.fc39 fedora 482 k Installing Groups: Buildsystem building group Transaction Summary ================================================================================ Install 152 Packages Total size: 52 M Installed size: 180 M Downloading Packages: [SKIPPED] jansson-2.13.1-7.fc40.x86_64.rpm: Already downloaded [SKIPPED] krb5-libs-1.21.2-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] alternatives-1.25-1.fc39.x86_64.rpm: Already downloaded [SKIPPED] ansible-srpm-macros-1-11.fc39.noarch.rpm: Already downloaded [SKIPPED] audit-libs-3.1.2-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] authselect-1.4.3-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] authselect-libs-1.4.3-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] basesystem-11-18.fc39.noarch.rpm: Already downloaded [SKIPPED] bash-5.2.21-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] binutils-2.41-14.fc40.x86_64.rpm: Already downloaded [SKIPPED] binutils-gold-2.41-14.fc40.x86_64.rpm: Already downloaded [SKIPPED] bzip2-1.0.8-16.fc39.x86_64.rpm: Already downloaded [SKIPPED] bzip2-libs-1.0.8-16.fc39.x86_64.rpm: Already downloaded [SKIPPED] ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch.rpm: Already downloaded [SKIPPED] coreutils-9.4-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] coreutils-common-9.4-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] cpio-2.14-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] cracklib-2.9.11-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] crypto-policies-20231113-1.gitb402e82.fc40.noarch.rpm: Already downloaded [SKIPPED] curl-8.4.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] cyrus-sasl-lib-2.1.28-11.fc39.x86_64.rpm: Already downloaded [SKIPPED] debugedit-5.0-11.fc40.x86_64.rpm: Already downloaded [SKIPPED] diffutils-3.10-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] dwz-0.15-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] ed-1.19-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] efi-srpm-macros-5-9.fc39.noarch.rpm: Already downloaded [SKIPPED] elfutils-0.190-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] elfutils-debuginfod-client-0.190-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] elfutils-default-yama-scope-0.190-2.fc40.noarch.rpm: Already downloaded [SKIPPED] elfutils-libelf-0.190-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] elfutils-libs-0.190-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] fedora-gpg-keys-40-0.2.noarch.rpm: Already downloaded [SKIPPED] fedora-release-40-0.20.noarch.rpm: Already downloaded [SKIPPED] fedora-release-common-40-0.20.noarch.rpm: Already downloaded [SKIPPED] fedora-release-identity-basic-40-0.20.noarch.rpm: Already downloaded [SKIPPED] fedora-repos-40-0.2.noarch.rpm: Already downloaded [SKIPPED] fedora-repos-rawhide-40-0.2.noarch.rpm: Already downloaded [SKIPPED] file-5.45-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] file-libs-5.45-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] filesystem-3.18-6.fc39.x86_64.rpm: Already downloaded [SKIPPED] findutils-4.9.0-6.fc40.x86_64.rpm: Already downloaded [SKIPPED] fonts-srpm-macros-2.0.5-12.fc39.noarch.rpm: Already downloaded [SKIPPED] forge-srpm-macros-0.1.0-1.fc40.noarch.rpm: Already downloaded [SKIPPED] fpc-srpm-macros-1.3-8.fc39.noarch.rpm: Already downloaded [SKIPPED] gawk-5.2.2-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] gdb-minimal-13.2-11.fc40.x86_64.rpm: Already downloaded [SKIPPED] gdbm-1.23-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] gdbm-libs-1.23-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] ghc-srpm-macros-1.6.1-3.fc40.noarch.rpm: Already downloaded [SKIPPED] glibc-2.38.9000-22.fc40.x86_64.rpm: Already downloaded [SKIPPED] glibc-common-2.38.9000-22.fc40.x86_64.rpm: Already downloaded [SKIPPED] glibc-gconv-extra-2.38.9000-22.fc40.x86_64.rpm: Already downloaded [SKIPPED] glibc-minimal-langpack-2.38.9000-22.fc40.x86_64.rpm: Already downloaded [SKIPPED] gmp-6.2.1-5.fc39.x86_64.rpm: Already downloaded [SKIPPED] gnat-srpm-macros-6-3.fc39.noarch.rpm: Already downloaded [SKIPPED] go-srpm-macros-3.3.1-1.fc40.noarch.rpm: Already downloaded [SKIPPED] grep-3.11-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] gzip-1.12-6.fc39.x86_64.rpm: Already downloaded [SKIPPED] info-7.1-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] kernel-srpm-macros-1.0-20.fc39.noarch.rpm: Already downloaded [SKIPPED] keyutils-libs-1.6.1-7.fc39.x86_64.rpm: Already downloaded [SKIPPED] libacl-2.3.1-10.fc40.x86_64.rpm: Already downloaded [SKIPPED] libarchive-3.7.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libattr-2.5.1-9.fc40.x86_64.rpm: Already downloaded [SKIPPED] libblkid-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libbrotli-1.1.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libcap-2.69-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libcap-ng-0.8.3-8.fc40.x86_64.rpm: Already downloaded [SKIPPED] libcom_err-1.47.0-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] libcurl-8.4.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libeconf-0.5.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libevent-2.1.12-9.fc39.x86_64.rpm: Already downloaded [SKIPPED] libfdisk-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libffi-3.4.4-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] libgcc-13.2.1-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] libgomp-13.2.1-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] libidn2-2.3.4-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] libmount-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libnghttp2-1.58.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libnsl2-2.0.0-6.fc39.x86_64.rpm: Already downloaded [SKIPPED] libpkgconf-1.9.5-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] libpsl-0.21.2-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] libpwquality-1.4.5-6.fc39.x86_64.rpm: Already downloaded [SKIPPED] libselinux-3.6-0.rc1.1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libsemanage-3.6-0.rc1.1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libsepol-3.6-0.rc1.1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libsigsegv-2.14-5.fc39.x86_64.rpm: Already downloaded [SKIPPED] libsmartcols-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libssh-0.10.5-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] libssh-config-0.10.5-2.fc39.noarch.rpm: Already downloaded [SKIPPED] libstdc++-13.2.1-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] libtasn1-4.19.0-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] libtirpc-1.3.4-0.fc40.x86_64.rpm: Already downloaded [SKIPPED] libunistring-1.1-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] libutempter-1.2.1-10.fc39.x86_64.rpm: Already downloaded [SKIPPED] libuuid-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libverto-0.3.2-6.fc39.x86_64.rpm: Already downloaded [SKIPPED] libxcrypt-4.4.36-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] libxml2-2.12.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] libzstd-1.5.5-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] lua-libs-5.4.6-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] lua-srpm-macros-1-9.fc39.noarch.rpm: Already downloaded [SKIPPED] lz4-libs-1.9.4-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] mpfr-4.2.1-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] ncurses-base-6.4-8.20231001.fc40.noarch.rpm: Already downloaded [SKIPPED] ncurses-libs-6.4-8.20231001.fc40.x86_64.rpm: Already downloaded [SKIPPED] ocaml-srpm-macros-9-1.fc40.noarch.rpm: Already downloaded [SKIPPED] openblas-srpm-macros-2-14.fc39.noarch.rpm: Already downloaded [SKIPPED] openldap-2.6.6-1.fc39.x86_64.rpm: Already downloaded [SKIPPED] openssl-libs-3.1.4-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] p11-kit-0.25.3-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] p11-kit-trust-0.25.3-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] package-notes-srpm-macros-0.5-9.fc39.noarch.rpm: Already downloaded [SKIPPED] pam-1.5.3-8.fc40.x86_64.rpm: Already downloaded [SKIPPED] pam-libs-1.5.3-8.fc40.x86_64.rpm: Already downloaded [SKIPPED] patch-2.7.6-22.fc39.x86_64.rpm: Already downloaded [SKIPPED] pcre2-10.42-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] pcre2-syntax-10.42-2.fc40.noarch.rpm: Already downloaded [SKIPPED] perl-srpm-macros-1-51.fc39.noarch.rpm: Already downloaded [SKIPPED] pkgconf-1.9.5-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] pkgconf-m4-1.9.5-2.fc39.noarch.rpm: Already downloaded [SKIPPED] pkgconf-pkg-config-1.9.5-2.fc39.x86_64.rpm: Already downloaded [SKIPPED] popt-1.19-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] publicsuffix-list-dafsa-20230812-1.fc40.noarch.rpm: Already downloaded [SKIPPED] pyproject-srpm-macros-1.10.0-1.fc40.noarch.rpm: Already downloaded [SKIPPED] python-srpm-macros-3.12-4.fc40.noarch.rpm: Already downloaded [SKIPPED] qt5-srpm-macros-5.15.11-1.fc40.noarch.rpm: Already downloaded [SKIPPED] qt6-srpm-macros-6.6.0-1.fc40.noarch.rpm: Already downloaded [SKIPPED] readline-8.2-4.fc39.x86_64.rpm: Already downloaded [SKIPPED] redhat-rpm-config-271-1.fc40.noarch.rpm: Already downloaded [SKIPPED] rpm-4.19.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] rpm-build-4.19.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] rpm-build-libs-4.19.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] rpm-libs-4.19.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] rpm-sequoia-1.5.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] rust-srpm-macros-25.2-2.fc40.noarch.rpm: Already downloaded [SKIPPED] sed-4.8-14.fc39.x86_64.rpm: Already downloaded [SKIPPED] setup-2.14.4-1.fc39.noarch.rpm: Already downloaded [SKIPPED] shadow-utils-4.14.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] sqlite-libs-3.44.0-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] systemd-libs-255~rc3-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] tar-1.35-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] unzip-6.0-62.fc39.x86_64.rpm: Already downloaded [SKIPPED] util-linux-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] util-linux-core-2.39.2-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] which-2.21-40.fc39.x86_64.rpm: Already downloaded [SKIPPED] xxhash-libs-0.8.2-1.fc39.x86_64.rpm: Already downloaded [SKIPPED] xz-5.4.5-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] xz-libs-5.4.5-1.fc40.x86_64.rpm: Already downloaded [SKIPPED] zip-3.0-39.fc40.x86_64.rpm: Already downloaded [SKIPPED] zlib-1.2.13-5.fc40.x86_64.rpm: Already downloaded [SKIPPED] zstd-1.5.5-4.fc39.x86_64.rpm: Already downloaded fedora 1.6 MB/s | 1.6 kB 00:00 Importing GPG key 0xA15B79CC: Userid : "Fedora (40) " Fingerprint: 115D F9AE F857 853E E844 5D0A 0727 707E A15B 79CC From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-40-primary Key imported successfully fedora 1.6 MB/s | 1.6 kB 00:00 GPG key at file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-40-primary (0xA15B79CC) is already installed fedora 1.6 MB/s | 1.6 kB 00:00 Importing GPG key 0x18B8E74C: Userid : "Fedora (39) " Fingerprint: E8F2 3996 F232 1864 0CB4 4CBE 75CF 5AC4 18B8 E74C From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-39-primary Key imported successfully Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: filesystem-3.18-6.fc39.x86_64 1/1 Preparing : 1/1 Installing : libgcc-13.2.1-5.fc40.x86_64 1/152 Running scriptlet: libgcc-13.2.1-5.fc40.x86_64 1/152 Installing : crypto-policies-20231113-1.gitb402e82.fc40.noarc 2/152 Running scriptlet: crypto-policies-20231113-1.gitb402e82.fc40.noarc 2/152 Installing : fedora-release-identity-basic-40-0.20.noarch 3/152 Installing : fedora-repos-rawhide-40-0.2.noarch 4/152 Installing : fedora-gpg-keys-40-0.2.noarch 5/152 Installing : fedora-repos-40-0.2.noarch 6/152 Installing : fedora-release-common-40-0.20.noarch 7/152 Installing : fedora-release-40-0.20.noarch 8/152 Installing : setup-2.14.4-1.fc39.noarch 9/152 warning: /etc/hosts created as /etc/hosts.rpmnew Running scriptlet: setup-2.14.4-1.fc39.noarch 9/152 Installing : filesystem-3.18-6.fc39.x86_64 10/152 Installing : basesystem-11-18.fc39.noarch 11/152 Installing : rust-srpm-macros-25.2-2.fc40.noarch 12/152 Installing : qt6-srpm-macros-6.6.0-1.fc40.noarch 13/152 Installing : qt5-srpm-macros-5.15.11-1.fc40.noarch 14/152 Installing : publicsuffix-list-dafsa-20230812-1.fc40.noarch 15/152 Installing : pkgconf-m4-1.9.5-2.fc39.noarch 16/152 Installing : perl-srpm-macros-1-51.fc39.noarch 17/152 Installing : pcre2-syntax-10.42-2.fc40.noarch 18/152 Installing : package-notes-srpm-macros-0.5-9.fc39.noarch 19/152 Installing : openblas-srpm-macros-2-14.fc39.noarch 20/152 Installing : ocaml-srpm-macros-9-1.fc40.noarch 21/152 Installing : ncurses-base-6.4-8.20231001.fc40.noarch 22/152 Installing : glibc-gconv-extra-2.38.9000-22.fc40.x86_64 23/152 Running scriptlet: glibc-gconv-extra-2.38.9000-22.fc40.x86_64 23/152 Installing : glibc-minimal-langpack-2.38.9000-22.fc40.x86_64 24/152 Installing : glibc-common-2.38.9000-22.fc40.x86_64 25/152 Running scriptlet: glibc-2.38.9000-22.fc40.x86_64 26/152 Installing : glibc-2.38.9000-22.fc40.x86_64 26/152 Running scriptlet: glibc-2.38.9000-22.fc40.x86_64 26/152 Installing : ncurses-libs-6.4-8.20231001.fc40.x86_64 27/152 Installing : bash-5.2.21-2.fc40.x86_64 28/152 Running scriptlet: bash-5.2.21-2.fc40.x86_64 28/152 Installing : zlib-1.2.13-5.fc40.x86_64 29/152 Installing : xz-libs-5.4.5-1.fc40.x86_64 30/152 Installing : bzip2-libs-1.0.8-16.fc39.x86_64 31/152 Installing : readline-8.2-4.fc39.x86_64 32/152 Installing : libstdc++-13.2.1-5.fc40.x86_64 33/152 Installing : libuuid-2.39.2-1.fc40.x86_64 34/152 Installing : libzstd-1.5.5-4.fc39.x86_64 35/152 Installing : elfutils-libelf-0.190-2.fc40.x86_64 36/152 Installing : popt-1.19-3.fc39.x86_64 37/152 Installing : libblkid-2.39.2-1.fc40.x86_64 38/152 Installing : gmp-1:6.2.1-5.fc39.x86_64 39/152 Installing : libattr-2.5.1-9.fc40.x86_64 40/152 Installing : libacl-2.3.1-10.fc40.x86_64 41/152 Installing : libxcrypt-4.4.36-2.fc39.x86_64 42/152 Installing : gdbm-libs-1:1.23-4.fc39.x86_64 43/152 Installing : libeconf-0.5.2-1.fc40.x86_64 44/152 Installing : lz4-libs-1.9.4-4.fc39.x86_64 45/152 Installing : mpfr-4.2.1-1.fc40.x86_64 46/152 Installing : dwz-0.15-3.fc39.x86_64 47/152 Installing : unzip-6.0-62.fc39.x86_64 48/152 Installing : file-libs-5.45-1.fc40.x86_64 49/152 Installing : file-5.45-1.fc40.x86_64 50/152 Installing : jansson-2.13.1-7.fc40.x86_64 51/152 Installing : alternatives-1.25-1.fc39.x86_64 52/152 Installing : libcap-ng-0.8.3-8.fc40.x86_64 53/152 Installing : audit-libs-3.1.2-5.fc40.x86_64 54/152 Installing : pam-libs-1.5.3-8.fc40.x86_64 55/152 Installing : libcap-2.69-1.fc40.x86_64 56/152 Installing : systemd-libs-255~rc3-1.fc40.x86_64 57/152 Installing : libcom_err-1.47.0-2.fc39.x86_64 58/152 Installing : libsepol-3.6-0.rc1.1.fc40.x86_64 59/152 Installing : libsmartcols-2.39.2-1.fc40.x86_64 60/152 Installing : libtasn1-4.19.0-3.fc39.x86_64 61/152 Installing : libunistring-1.1-5.fc40.x86_64 62/152 Installing : libidn2-2.3.4-3.fc39.x86_64 63/152 Installing : lua-libs-5.4.6-3.fc39.x86_64 64/152 Installing : pcre2-10.42-2.fc40.x86_64 65/152 Installing : libselinux-3.6-0.rc1.1.fc40.x86_64 66/152 Installing : sed-4.8-14.fc39.x86_64 67/152 Installing : grep-3.11-5.fc40.x86_64 68/152 Installing : findutils-1:4.9.0-6.fc40.x86_64 69/152 Installing : xz-5.4.5-1.fc40.x86_64 70/152 Installing : libmount-2.39.2-1.fc40.x86_64 71/152 Installing : util-linux-core-2.39.2-1.fc40.x86_64 72/152 Installing : libsemanage-3.6-0.rc1.1.fc40.x86_64 73/152 Installing : shadow-utils-2:4.14.0-2.fc40.x86_64 74/152 Running scriptlet: libutempter-1.2.1-10.fc39.x86_64 75/152 Installing : libutempter-1.2.1-10.fc39.x86_64 75/152 Installing : tar-2:1.35-2.fc40.x86_64 76/152 Installing : libpsl-0.21.2-4.fc39.x86_64 77/152 Installing : zip-3.0-39.fc40.x86_64 78/152 Installing : zstd-1.5.5-4.fc39.x86_64 79/152 Installing : cyrus-sasl-lib-2.1.28-11.fc39.x86_64 80/152 Installing : gdbm-1:1.23-4.fc39.x86_64 81/152 Installing : libfdisk-2.39.2-1.fc40.x86_64 82/152 Installing : bzip2-1.0.8-16.fc39.x86_64 83/152 Installing : libxml2-2.12.0-1.fc40.x86_64 84/152 Installing : sqlite-libs-3.44.0-1.fc40.x86_64 85/152 Installing : ed-1.19-4.fc39.x86_64 86/152 Installing : patch-2.7.6-22.fc39.x86_64 87/152 Installing : elfutils-default-yama-scope-0.190-2.fc40.noarch 88/152 Running scriptlet: elfutils-default-yama-scope-0.190-2.fc40.noarch 88/152 Installing : cpio-2.14-5.fc40.x86_64 89/152 Installing : diffutils-3.10-3.fc39.x86_64 90/152 Installing : keyutils-libs-1.6.1-7.fc39.x86_64 91/152 Installing : libbrotli-1.1.0-1.fc40.x86_64 92/152 Installing : libffi-3.4.4-4.fc39.x86_64 93/152 Installing : p11-kit-0.25.3-1.fc40.x86_64 94/152 Installing : p11-kit-trust-0.25.3-1.fc40.x86_64 95/152 Running scriptlet: p11-kit-trust-0.25.3-1.fc40.x86_64 95/152 Installing : libgomp-13.2.1-5.fc40.x86_64 96/152 Installing : libnghttp2-1.58.0-1.fc40.x86_64 97/152 Installing : libpkgconf-1.9.5-2.fc39.x86_64 98/152 Installing : pkgconf-1.9.5-2.fc39.x86_64 99/152 Installing : pkgconf-pkg-config-1.9.5-2.fc39.x86_64 100/152 Installing : libsigsegv-2.14-5.fc39.x86_64 101/152 Installing : gawk-5.2.2-2.fc39.x86_64 102/152 Installing : libverto-0.3.2-6.fc39.x86_64 103/152 Installing : xxhash-libs-0.8.2-1.fc39.x86_64 104/152 Installing : libssh-config-0.10.5-2.fc39.noarch 105/152 Installing : kernel-srpm-macros-1.0-20.fc39.noarch 106/152 Installing : gnat-srpm-macros-6-3.fc39.noarch 107/152 Installing : ghc-srpm-macros-1.6.1-3.fc40.noarch 108/152 Installing : fpc-srpm-macros-1.3-8.fc39.noarch 109/152 Installing : coreutils-common-9.4-1.fc40.x86_64 110/152 Installing : openssl-libs-1:3.1.4-1.fc40.x86_64 111/152 Installing : coreutils-9.4-1.fc40.x86_64 112/152 Running scriptlet: ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch 113/152 Installing : ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch 113/152 Running scriptlet: ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch 113/152 Installing : krb5-libs-1.21.2-2.fc40.x86_64 114/152 Installing : libtirpc-1.3.4-0.fc40.x86_64 115/152 Running scriptlet: authselect-libs-1.4.3-1.fc40.x86_64 116/152 Installing : authselect-libs-1.4.3-1.fc40.x86_64 116/152 Installing : gzip-1.12-6.fc39.x86_64 117/152 Installing : cracklib-2.9.11-2.fc39.x86_64 118/152 Installing : libpwquality-1.4.5-6.fc39.x86_64 119/152 Installing : authselect-1.4.3-1.fc40.x86_64 120/152 Installing : libnsl2-2.0.0-6.fc39.x86_64 121/152 Installing : pam-1.5.3-8.fc40.x86_64 122/152 Installing : libssh-0.10.5-2.fc39.x86_64 123/152 Installing : libarchive-3.7.2-1.fc40.x86_64 124/152 Installing : libevent-2.1.12-9.fc39.x86_64 125/152 Installing : openldap-2.6.6-1.fc39.x86_64 126/152 Installing : libcurl-8.4.0-1.fc40.x86_64 127/152 Installing : elfutils-libs-0.190-2.fc40.x86_64 128/152 Installing : elfutils-debuginfod-client-0.190-2.fc40.x86_64 129/152 Installing : binutils-2.41-14.fc40.x86_64 130/152 Running scriptlet: binutils-2.41-14.fc40.x86_64 130/152 Installing : binutils-gold-2.41-14.fc40.x86_64 131/152 Running scriptlet: binutils-gold-2.41-14.fc40.x86_64 131/152 Installing : elfutils-0.190-2.fc40.x86_64 132/152 Installing : gdb-minimal-13.2-11.fc40.x86_64 133/152 Installing : debugedit-5.0-11.fc40.x86_64 134/152 Installing : curl-8.4.0-1.fc40.x86_64 135/152 Installing : rpm-sequoia-1.5.0-1.fc40.x86_64 136/152 Installing : rpm-libs-4.19.0-2.fc40.x86_64 137/152 Running scriptlet: rpm-4.19.0-2.fc40.x86_64 138/152 Installing : rpm-4.19.0-2.fc40.x86_64 138/152 Installing : efi-srpm-macros-5-9.fc39.noarch 139/152 Installing : lua-srpm-macros-1-9.fc39.noarch 140/152 Installing : rpm-build-libs-4.19.0-2.fc40.x86_64 141/152 Installing : ansible-srpm-macros-1-11.fc39.noarch 142/152 Installing : fonts-srpm-macros-1:2.0.5-12.fc39.noarch 143/152 Installing : forge-srpm-macros-0.1.0-1.fc40.noarch 144/152 Installing : go-srpm-macros-3.3.1-1.fc40.noarch 145/152 Installing : python-srpm-macros-3.12-4.fc40.noarch 146/152 Installing : redhat-rpm-config-271-1.fc40.noarch 147/152 Installing : rpm-build-4.19.0-2.fc40.x86_64 148/152 Installing : pyproject-srpm-macros-1.10.0-1.fc40.noarch 149/152 Installing : util-linux-2.39.2-1.fc40.x86_64 150/152 Installing : which-2.21-40.fc39.x86_64 151/152 Installing : info-7.1-1.fc40.x86_64 152/152 Running scriptlet: filesystem-3.18-6.fc39.x86_64 152/152 Running scriptlet: ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch 152/152 Running scriptlet: authselect-libs-1.4.3-1.fc40.x86_64 152/152 Running scriptlet: rpm-4.19.0-2.fc40.x86_64 152/152 Running scriptlet: info-7.1-1.fc40.x86_64 152/152 Installed: alternatives-1.25-1.fc39.x86_64 ansible-srpm-macros-1-11.fc39.noarch audit-libs-3.1.2-5.fc40.x86_64 authselect-1.4.3-1.fc40.x86_64 authselect-libs-1.4.3-1.fc40.x86_64 basesystem-11-18.fc39.noarch bash-5.2.21-2.fc40.x86_64 binutils-2.41-14.fc40.x86_64 binutils-gold-2.41-14.fc40.x86_64 bzip2-1.0.8-16.fc39.x86_64 bzip2-libs-1.0.8-16.fc39.x86_64 ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch coreutils-9.4-1.fc40.x86_64 coreutils-common-9.4-1.fc40.x86_64 cpio-2.14-5.fc40.x86_64 cracklib-2.9.11-2.fc39.x86_64 crypto-policies-20231113-1.gitb402e82.fc40.noarch curl-8.4.0-1.fc40.x86_64 cyrus-sasl-lib-2.1.28-11.fc39.x86_64 debugedit-5.0-11.fc40.x86_64 diffutils-3.10-3.fc39.x86_64 dwz-0.15-3.fc39.x86_64 ed-1.19-4.fc39.x86_64 efi-srpm-macros-5-9.fc39.noarch elfutils-0.190-2.fc40.x86_64 elfutils-debuginfod-client-0.190-2.fc40.x86_64 elfutils-default-yama-scope-0.190-2.fc40.noarch elfutils-libelf-0.190-2.fc40.x86_64 elfutils-libs-0.190-2.fc40.x86_64 fedora-gpg-keys-40-0.2.noarch fedora-release-40-0.20.noarch fedora-release-common-40-0.20.noarch fedora-release-identity-basic-40-0.20.noarch fedora-repos-40-0.2.noarch fedora-repos-rawhide-40-0.2.noarch file-5.45-1.fc40.x86_64 file-libs-5.45-1.fc40.x86_64 filesystem-3.18-6.fc39.x86_64 findutils-1:4.9.0-6.fc40.x86_64 fonts-srpm-macros-1:2.0.5-12.fc39.noarch forge-srpm-macros-0.1.0-1.fc40.noarch fpc-srpm-macros-1.3-8.fc39.noarch gawk-5.2.2-2.fc39.x86_64 gdb-minimal-13.2-11.fc40.x86_64 gdbm-1:1.23-4.fc39.x86_64 gdbm-libs-1:1.23-4.fc39.x86_64 ghc-srpm-macros-1.6.1-3.fc40.noarch glibc-2.38.9000-22.fc40.x86_64 glibc-common-2.38.9000-22.fc40.x86_64 glibc-gconv-extra-2.38.9000-22.fc40.x86_64 glibc-minimal-langpack-2.38.9000-22.fc40.x86_64 gmp-1:6.2.1-5.fc39.x86_64 gnat-srpm-macros-6-3.fc39.noarch go-srpm-macros-3.3.1-1.fc40.noarch grep-3.11-5.fc40.x86_64 gzip-1.12-6.fc39.x86_64 info-7.1-1.fc40.x86_64 jansson-2.13.1-7.fc40.x86_64 kernel-srpm-macros-1.0-20.fc39.noarch keyutils-libs-1.6.1-7.fc39.x86_64 krb5-libs-1.21.2-2.fc40.x86_64 libacl-2.3.1-10.fc40.x86_64 libarchive-3.7.2-1.fc40.x86_64 libattr-2.5.1-9.fc40.x86_64 libblkid-2.39.2-1.fc40.x86_64 libbrotli-1.1.0-1.fc40.x86_64 libcap-2.69-1.fc40.x86_64 libcap-ng-0.8.3-8.fc40.x86_64 libcom_err-1.47.0-2.fc39.x86_64 libcurl-8.4.0-1.fc40.x86_64 libeconf-0.5.2-1.fc40.x86_64 libevent-2.1.12-9.fc39.x86_64 libfdisk-2.39.2-1.fc40.x86_64 libffi-3.4.4-4.fc39.x86_64 libgcc-13.2.1-5.fc40.x86_64 libgomp-13.2.1-5.fc40.x86_64 libidn2-2.3.4-3.fc39.x86_64 libmount-2.39.2-1.fc40.x86_64 libnghttp2-1.58.0-1.fc40.x86_64 libnsl2-2.0.0-6.fc39.x86_64 libpkgconf-1.9.5-2.fc39.x86_64 libpsl-0.21.2-4.fc39.x86_64 libpwquality-1.4.5-6.fc39.x86_64 libselinux-3.6-0.rc1.1.fc40.x86_64 libsemanage-3.6-0.rc1.1.fc40.x86_64 libsepol-3.6-0.rc1.1.fc40.x86_64 libsigsegv-2.14-5.fc39.x86_64 libsmartcols-2.39.2-1.fc40.x86_64 libssh-0.10.5-2.fc39.x86_64 libssh-config-0.10.5-2.fc39.noarch libstdc++-13.2.1-5.fc40.x86_64 libtasn1-4.19.0-3.fc39.x86_64 libtirpc-1.3.4-0.fc40.x86_64 libunistring-1.1-5.fc40.x86_64 libutempter-1.2.1-10.fc39.x86_64 libuuid-2.39.2-1.fc40.x86_64 libverto-0.3.2-6.fc39.x86_64 libxcrypt-4.4.36-2.fc39.x86_64 libxml2-2.12.0-1.fc40.x86_64 libzstd-1.5.5-4.fc39.x86_64 lua-libs-5.4.6-3.fc39.x86_64 lua-srpm-macros-1-9.fc39.noarch lz4-libs-1.9.4-4.fc39.x86_64 mpfr-4.2.1-1.fc40.x86_64 ncurses-base-6.4-8.20231001.fc40.noarch ncurses-libs-6.4-8.20231001.fc40.x86_64 ocaml-srpm-macros-9-1.fc40.noarch openblas-srpm-macros-2-14.fc39.noarch openldap-2.6.6-1.fc39.x86_64 openssl-libs-1:3.1.4-1.fc40.x86_64 p11-kit-0.25.3-1.fc40.x86_64 p11-kit-trust-0.25.3-1.fc40.x86_64 package-notes-srpm-macros-0.5-9.fc39.noarch pam-1.5.3-8.fc40.x86_64 pam-libs-1.5.3-8.fc40.x86_64 patch-2.7.6-22.fc39.x86_64 pcre2-10.42-2.fc40.x86_64 pcre2-syntax-10.42-2.fc40.noarch perl-srpm-macros-1-51.fc39.noarch pkgconf-1.9.5-2.fc39.x86_64 pkgconf-m4-1.9.5-2.fc39.noarch pkgconf-pkg-config-1.9.5-2.fc39.x86_64 popt-1.19-3.fc39.x86_64 publicsuffix-list-dafsa-20230812-1.fc40.noarch pyproject-srpm-macros-1.10.0-1.fc40.noarch python-srpm-macros-3.12-4.fc40.noarch qt5-srpm-macros-5.15.11-1.fc40.noarch qt6-srpm-macros-6.6.0-1.fc40.noarch readline-8.2-4.fc39.x86_64 redhat-rpm-config-271-1.fc40.noarch rpm-4.19.0-2.fc40.x86_64 rpm-build-4.19.0-2.fc40.x86_64 rpm-build-libs-4.19.0-2.fc40.x86_64 rpm-libs-4.19.0-2.fc40.x86_64 rpm-sequoia-1.5.0-1.fc40.x86_64 rust-srpm-macros-25.2-2.fc40.noarch sed-4.8-14.fc39.x86_64 setup-2.14.4-1.fc39.noarch shadow-utils-2:4.14.0-2.fc40.x86_64 sqlite-libs-3.44.0-1.fc40.x86_64 systemd-libs-255~rc3-1.fc40.x86_64 tar-2:1.35-2.fc40.x86_64 unzip-6.0-62.fc39.x86_64 util-linux-2.39.2-1.fc40.x86_64 util-linux-core-2.39.2-1.fc40.x86_64 which-2.21-40.fc39.x86_64 xxhash-libs-0.8.2-1.fc39.x86_64 xz-5.4.5-1.fc40.x86_64 xz-libs-5.4.5-1.fc40.x86_64 zip-3.0-39.fc40.x86_64 zlib-1.2.13-5.fc40.x86_64 zstd-1.5.5-4.fc39.x86_64 Complete! Finish: installing minimal buildroot with dnf Start: creating root cache Finish: creating root cache Finish: chroot init INFO: Installed packages: INFO: alternatives-1.25-1.fc39.x86_64 ansible-srpm-macros-1-11.fc39.noarch audit-libs-3.1.2-5.fc40.x86_64 authselect-1.4.3-1.fc40.x86_64 authselect-libs-1.4.3-1.fc40.x86_64 basesystem-11-18.fc39.noarch bash-5.2.21-2.fc40.x86_64 binutils-2.41-14.fc40.x86_64 binutils-gold-2.41-14.fc40.x86_64 bzip2-1.0.8-16.fc39.x86_64 bzip2-libs-1.0.8-16.fc39.x86_64 ca-certificates-2023.2.62_v7.0.401-4.fc40.noarch coreutils-9.4-1.fc40.x86_64 coreutils-common-9.4-1.fc40.x86_64 cpio-2.14-5.fc40.x86_64 cracklib-2.9.11-2.fc39.x86_64 crypto-policies-20231113-1.gitb402e82.fc40.noarch curl-8.4.0-1.fc40.x86_64 cyrus-sasl-lib-2.1.28-11.fc39.x86_64 debugedit-5.0-11.fc40.x86_64 diffutils-3.10-3.fc39.x86_64 dwz-0.15-3.fc39.x86_64 ed-1.19-4.fc39.x86_64 efi-srpm-macros-5-9.fc39.noarch elfutils-0.190-2.fc40.x86_64 elfutils-debuginfod-client-0.190-2.fc40.x86_64 elfutils-default-yama-scope-0.190-2.fc40.noarch elfutils-libelf-0.190-2.fc40.x86_64 elfutils-libs-0.190-2.fc40.x86_64 fedora-gpg-keys-40-0.2.noarch fedora-release-40-0.20.noarch fedora-release-common-40-0.20.noarch fedora-release-identity-basic-40-0.20.noarch fedora-repos-40-0.2.noarch fedora-repos-rawhide-40-0.2.noarch file-5.45-1.fc40.x86_64 file-libs-5.45-1.fc40.x86_64 filesystem-3.18-6.fc39.x86_64 findutils-4.9.0-6.fc40.x86_64 fonts-srpm-macros-2.0.5-12.fc39.noarch forge-srpm-macros-0.1.0-1.fc40.noarch fpc-srpm-macros-1.3-8.fc39.noarch gawk-5.2.2-2.fc39.x86_64 gdb-minimal-13.2-11.fc40.x86_64 gdbm-1.23-4.fc39.x86_64 gdbm-libs-1.23-4.fc39.x86_64 ghc-srpm-macros-1.6.1-3.fc40.noarch glibc-2.38.9000-22.fc40.x86_64 glibc-common-2.38.9000-22.fc40.x86_64 glibc-gconv-extra-2.38.9000-22.fc40.x86_64 glibc-minimal-langpack-2.38.9000-22.fc40.x86_64 gmp-6.2.1-5.fc39.x86_64 gnat-srpm-macros-6-3.fc39.noarch go-srpm-macros-3.3.1-1.fc40.noarch gpg-pubkey-18b8e74c-62f2920f gpg-pubkey-a15b79cc-63d04c2c grep-3.11-5.fc40.x86_64 gzip-1.12-6.fc39.x86_64 info-7.1-1.fc40.x86_64 jansson-2.13.1-7.fc40.x86_64 kernel-srpm-macros-1.0-20.fc39.noarch keyutils-libs-1.6.1-7.fc39.x86_64 krb5-libs-1.21.2-2.fc40.x86_64 libacl-2.3.1-10.fc40.x86_64 libarchive-3.7.2-1.fc40.x86_64 libattr-2.5.1-9.fc40.x86_64 libblkid-2.39.2-1.fc40.x86_64 libbrotli-1.1.0-1.fc40.x86_64 libcap-2.69-1.fc40.x86_64 libcap-ng-0.8.3-8.fc40.x86_64 libcom_err-1.47.0-2.fc39.x86_64 libcurl-8.4.0-1.fc40.x86_64 libeconf-0.5.2-1.fc40.x86_64 libevent-2.1.12-9.fc39.x86_64 libfdisk-2.39.2-1.fc40.x86_64 libffi-3.4.4-4.fc39.x86_64 libgcc-13.2.1-5.fc40.x86_64 libgomp-13.2.1-5.fc40.x86_64 libidn2-2.3.4-3.fc39.x86_64 libmount-2.39.2-1.fc40.x86_64 libnghttp2-1.58.0-1.fc40.x86_64 libnsl2-2.0.0-6.fc39.x86_64 libpkgconf-1.9.5-2.fc39.x86_64 libpsl-0.21.2-4.fc39.x86_64 libpwquality-1.4.5-6.fc39.x86_64 libselinux-3.6-0.rc1.1.fc40.x86_64 libsemanage-3.6-0.rc1.1.fc40.x86_64 libsepol-3.6-0.rc1.1.fc40.x86_64 libsigsegv-2.14-5.fc39.x86_64 libsmartcols-2.39.2-1.fc40.x86_64 libssh-0.10.5-2.fc39.x86_64 libssh-config-0.10.5-2.fc39.noarch libstdc++-13.2.1-5.fc40.x86_64 libtasn1-4.19.0-3.fc39.x86_64 libtirpc-1.3.4-0.fc40.x86_64 libunistring-1.1-5.fc40.x86_64 libutempter-1.2.1-10.fc39.x86_64 libuuid-2.39.2-1.fc40.x86_64 libverto-0.3.2-6.fc39.x86_64 libxcrypt-4.4.36-2.fc39.x86_64 libxml2-2.12.0-1.fc40.x86_64 libzstd-1.5.5-4.fc39.x86_64 lua-libs-5.4.6-3.fc39.x86_64 lua-srpm-macros-1-9.fc39.noarch lz4-libs-1.9.4-4.fc39.x86_64 mpfr-4.2.1-1.fc40.x86_64 ncurses-base-6.4-8.20231001.fc40.noarch ncurses-libs-6.4-8.20231001.fc40.x86_64 ocaml-srpm-macros-9-1.fc40.noarch openblas-srpm-macros-2-14.fc39.noarch openldap-2.6.6-1.fc39.x86_64 openssl-libs-3.1.4-1.fc40.x86_64 p11-kit-0.25.3-1.fc40.x86_64 p11-kit-trust-0.25.3-1.fc40.x86_64 package-notes-srpm-macros-0.5-9.fc39.noarch pam-1.5.3-8.fc40.x86_64 pam-libs-1.5.3-8.fc40.x86_64 patch-2.7.6-22.fc39.x86_64 pcre2-10.42-2.fc40.x86_64 pcre2-syntax-10.42-2.fc40.noarch perl-srpm-macros-1-51.fc39.noarch pkgconf-1.9.5-2.fc39.x86_64 pkgconf-m4-1.9.5-2.fc39.noarch pkgconf-pkg-config-1.9.5-2.fc39.x86_64 popt-1.19-3.fc39.x86_64 publicsuffix-list-dafsa-20230812-1.fc40.noarch pyproject-srpm-macros-1.10.0-1.fc40.noarch python-srpm-macros-3.12-4.fc40.noarch qt5-srpm-macros-5.15.11-1.fc40.noarch qt6-srpm-macros-6.6.0-1.fc40.noarch readline-8.2-4.fc39.x86_64 redhat-rpm-config-271-1.fc40.noarch rpm-4.19.0-2.fc40.x86_64 rpm-build-4.19.0-2.fc40.x86_64 rpm-build-libs-4.19.0-2.fc40.x86_64 rpm-libs-4.19.0-2.fc40.x86_64 rpm-sequoia-1.5.0-1.fc40.x86_64 rust-srpm-macros-25.2-2.fc40.noarch sed-4.8-14.fc39.x86_64 setup-2.14.4-1.fc39.noarch shadow-utils-4.14.0-2.fc40.x86_64 sqlite-libs-3.44.0-1.fc40.x86_64 systemd-libs-255~rc3-1.fc40.x86_64 tar-1.35-2.fc40.x86_64 unzip-6.0-62.fc39.x86_64 util-linux-2.39.2-1.fc40.x86_64 util-linux-core-2.39.2-1.fc40.x86_64 which-2.21-40.fc39.x86_64 xxhash-libs-0.8.2-1.fc39.x86_64 xz-5.4.5-1.fc40.x86_64 xz-libs-5.4.5-1.fc40.x86_64 zip-3.0-39.fc40.x86_64 zlib-1.2.13-5.fc40.x86_64 zstd-1.5.5-4.fc39.x86_64 Start: buildsrpm Start: rpmbuild -bs Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.src.rpm Finish: rpmbuild -bs INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-rawhide-x86_64-1700753703.420278/root/var/log/dnf.rpm.log /var/lib/mock/fedora-rawhide-x86_64-1700753703.420278/root/var/log/dnf.librepo.log /var/lib/mock/fedora-rawhide-x86_64-1700753703.420278/root/var/log/dnf.log Finish: buildsrpm INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-pknhjbqd/python-django-mailman3/python-django-mailman3.spec) Config(child) 0 minutes 29 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-django-mailman3-1.3.9-1.fc40.src.rpm) Config(fedora-rawhide-x86_64) Start(bootstrap): chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1700753703.420278/root. INFO: reusing tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1700753703.420278/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-1700753703.420278/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 Finish: chroot init INFO: Buildroot is handled by package management downloaded with a bootstrap image: rpm-4.19.0-2.fc40.x86_64 rpm-sequoia-1.5.0-1.fc40.x86_64 python3-dnf-4.18.1-2.fc40.noarch python3-dnf-plugins-core-4.4.3-1.fc40.noarch yum-4.18.1-2.fc40.noarch Start: build phase for python-django-mailman3-1.3.9-1.fc40.src.rpm Start: build setup for python-django-mailman3-1.3.9-1.fc40.src.rpm Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.src.rpm No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 77 kB/s | 1.5 kB 00:00 Copr repository 55 MB/s | 3.5 MB 00:00 fedora 74 kB/s | 20 kB 00:00 Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: python3-devel x86_64 3.12.0-2.fc40 fedora 311 k python3-setuptools noarch 68.2.2-1.fc40 fedora 1.5 M Installing dependencies: expat x86_64 2.5.0-3.fc39 fedora 110 k libb2 x86_64 0.98.1-9.fc39 fedora 25 k mpdecimal x86_64 2.5.1-7.fc39 fedora 89 k pyproject-rpm-macros noarch 1.10.0-1.fc40 fedora 41 k python-pip-wheel noarch 23.2.1-1.fc39 fedora 1.5 M python-rpm-macros noarch 3.12-4.fc40 fedora 19 k python3 x86_64 3.12.0-2.fc40 fedora 26 k python3-libs x86_64 3.12.0-2.fc40 fedora 9.2 M python3-packaging noarch 23.2-2.fc40 fedora 125 k python3-rpm-generators noarch 14-8.fc40 fedora 30 k python3-rpm-macros noarch 3.12-4.fc40 fedora 14 k tzdata noarch 2023c-4.fc40 fedora 717 k Transaction Summary ================================================================================ Install 14 Packages Total size: 14 M Installed size: 54 M Downloading Packages: [SKIPPED] expat-2.5.0-3.fc39.x86_64.rpm: Already downloaded [SKIPPED] libb2-0.98.1-9.fc39.x86_64.rpm: Already downloaded [SKIPPED] mpdecimal-2.5.1-7.fc39.x86_64.rpm: Already downloaded [SKIPPED] pyproject-rpm-macros-1.10.0-1.fc40.noarch.rpm: Already downloaded [SKIPPED] python-pip-wheel-23.2.1-1.fc39.noarch.rpm: Already downloaded [SKIPPED] python-rpm-macros-3.12-4.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-3.12.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] python3-devel-3.12.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] python3-libs-3.12.0-2.fc40.x86_64.rpm: Already downloaded [SKIPPED] python3-packaging-23.2-2.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-rpm-generators-14-8.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-rpm-macros-3.12-4.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-setuptools-68.2.2-1.fc40.noarch.rpm: Already downloaded [SKIPPED] tzdata-2023c-4.fc40.noarch.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python-rpm-macros-3.12-4.fc40.noarch 1/14 Installing : python3-rpm-macros-3.12-4.fc40.noarch 2/14 Installing : pyproject-rpm-macros-1.10.0-1.fc40.noarch 3/14 Installing : tzdata-2023c-4.fc40.noarch 4/14 Installing : python-pip-wheel-23.2.1-1.fc39.noarch 5/14 Installing : mpdecimal-2.5.1-7.fc39.x86_64 6/14 Installing : libb2-0.98.1-9.fc39.x86_64 7/14 Installing : expat-2.5.0-3.fc39.x86_64 8/14 Installing : python3-3.12.0-2.fc40.x86_64 9/14 Installing : python3-libs-3.12.0-2.fc40.x86_64 10/14 Installing : python3-packaging-23.2-2.fc40.noarch 11/14 Installing : python3-rpm-generators-14-8.fc40.noarch 12/14 Installing : python3-devel-3.12.0-2.fc40.x86_64 13/14 Installing : python3-setuptools-68.2.2-1.fc40.noarch 14/14 Running scriptlet: python3-setuptools-68.2.2-1.fc40.noarch 14/14 Installed: expat-2.5.0-3.fc39.x86_64 libb2-0.98.1-9.fc39.x86_64 mpdecimal-2.5.1-7.fc39.x86_64 pyproject-rpm-macros-1.10.0-1.fc40.noarch python-pip-wheel-23.2.1-1.fc39.noarch python-rpm-macros-3.12-4.fc40.noarch python3-3.12.0-2.fc40.x86_64 python3-devel-3.12.0-2.fc40.x86_64 python3-libs-3.12.0-2.fc40.x86_64 python3-packaging-23.2-2.fc40.noarch python3-rpm-generators-14-8.fc40.noarch python3-rpm-macros-3.12-4.fc40.noarch python3-setuptools-68.2.2-1.fc40.noarch tzdata-2023c-4.fc40.noarch Complete! Finish: build setup for python-django-mailman3-1.3.9-1.fc40.src.rpm Start: rpmbuild python-django-mailman3-1.3.9-1.fc40.src.rpm Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Q6n2WV + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-mailman3-1.3.9 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-mailman3-1.3.9.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-mailman3-1.3.9 + rm -rf /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-django42.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-py312-no-assertEquals.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.jnp4RN + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + echo 'python3dist(wheel)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + RPM_TOXENV=py312 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.2.2) Handling wheel from default build backend Requirement not satisfied: wheel Exiting dependency generation pass: build backend + cat /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 54 kB/s | 1.5 kB 00:00 fedora 318 kB/s | 20 kB 00:00 Package pyproject-rpm-macros-1.10.0-1.fc40.noarch is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package python3-packaging-23.2-2.fc40.noarch is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: python3-pip noarch 23.2.1-1.fc39 fedora 3.1 M python3-wheel noarch 1:0.41.2-1.fc40 fedora 163 k Transaction Summary ================================================================================ Install 2 Packages Total size: 3.3 M Installed size: 14 M Downloading Packages: [SKIPPED] python3-pip-23.2.1-1.fc39.noarch.rpm: Already downloaded [SKIPPED] python3-wheel-0.41.2-1.fc40.noarch.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python3-wheel-1:0.41.2-1.fc40.noarch 1/2 Installing : python3-pip-23.2.1-1.fc39.noarch 2/2 Running scriptlet: python3-pip-23.2.1-1.fc39.noarch 2/2 Installed: python3-pip-23.2.1-1.fc39.noarch python3-wheel-1:0.41.2-1.fc40.noarch Complete! Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Wj54Cb + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-mailman3-1.3.9 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-mailman3-1.3.9.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-mailman3-1.3.9 + rm -rf /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-django42.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-py312-no-assertEquals.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.FgmJMt + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + echo 'python3dist(wheel)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + RPM_TOXENV=py312 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.2.2) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) running egg_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling tox-current-env >= 0.0.6 from tox itself Requirement not satisfied: tox-current-env >= 0.0.6 Exiting dependency generation pass: tox itself + cat /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 85 kB/s | 1.5 kB 00:00 fedora 66 kB/s | 20 kB 00:00 Package pyproject-rpm-macros-1.10.0-1.fc40.noarch is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package python3-packaging-23.2-2.fc40.noarch is already installed. Package python3-pip-23.2.1-1.fc39.noarch is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package python3-wheel-1:0.41.2-1.fc40.noarch is already installed. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: python3-tox-current-env noarch 0.0.11-5.fc39 fedora 34 k Installing dependencies: python-setuptools-wheel noarch 68.2.2-1.fc40 fedora 670 k python-wheel-wheel noarch 1:0.41.2-1.fc40 fedora 70 k python3-cachetools noarch 5.3.2-1.fc40 fedora 37 k python3-chardet noarch 5.2.0-1.fc40 copr_base 274 k python3-colorama noarch 0.4.6-5.fc40 fedora 71 k python3-distlib noarch 0.3.7-1.fc40 fedora 262 k python3-filelock noarch 3.12.2-1.fc39 fedora 35 k python3-platformdirs noarch 3.9.1-2.fc39 fedora 45 k python3-pluggy noarch 1.3.0-1.fc40 fedora 56 k python3-pyproject-api noarch 1.6.1-1.fc40 fedora 42 k python3-virtualenv noarch 20.21.1-5.fc40 fedora 304 k tox noarch 4.11.1-1.fc40 fedora 393 k Transaction Summary ================================================================================ Install 13 Packages Total size: 2.2 M Total download size: 2.2 M Installed size: 6.6 M Downloading Packages: [SKIPPED] python3-pluggy-1.3.0-1.fc40.noarch.rpm: Already downloaded (2/13): python3-chardet-5.2.0-1.fc40.noarch.rpm 15 MB/s | 274 kB 00:00 (3/13): python-wheel-wheel-0.41.2-1.fc40.noarch 1.1 MB/s | 70 kB 00:00 (4/13): python3-cachetools-5.3.2-1.fc40.noarch. 760 kB/s | 37 kB 00:00 (5/13): python3-colorama-0.4.6-5.fc40.noarch.rp 3.1 MB/s | 71 kB 00:00 (6/13): python3-filelock-3.12.2-1.fc39.noarch.r 2.8 MB/s | 35 kB 00:00 (7/13): python3-distlib-0.3.7-1.fc40.noarch.rpm 5.9 MB/s | 262 kB 00:00 (8/13): python3-platformdirs-3.9.1-2.fc39.noarc 3.4 MB/s | 45 kB 00:00 (9/13): python3-pyproject-api-1.6.1-1.fc40.noar 3.8 MB/s | 42 kB 00:00 (10/13): python-setuptools-wheel-68.2.2-1.fc40. 5.2 MB/s | 670 kB 00:00 (11/13): python3-tox-current-env-0.0.11-5.fc39. 2.7 MB/s | 34 kB 00:00 (12/13): python3-virtualenv-20.21.1-5.fc40.noar 17 MB/s | 304 kB 00:00 (13/13): tox-4.11.1-1.fc40.noarch.rpm 23 MB/s | 393 kB 00:00 -------------------------------------------------------------------------------- Total 10 MB/s | 2.2 MB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python3-platformdirs-3.9.1-2.fc39.noarch 1/13 Installing : python3-filelock-3.12.2-1.fc39.noarch 2/13 Installing : python3-pyproject-api-1.6.1-1.fc40.noarch 3/13 Installing : python3-pluggy-1.3.0-1.fc40.noarch 4/13 Installing : python3-distlib-0.3.7-1.fc40.noarch 5/13 Installing : python3-colorama-0.4.6-5.fc40.noarch 6/13 Installing : python3-cachetools-5.3.2-1.fc40.noarch 7/13 Installing : python-wheel-wheel-1:0.41.2-1.fc40.noarch 8/13 Installing : python-setuptools-wheel-68.2.2-1.fc40.noarch 9/13 Installing : python3-virtualenv-20.21.1-5.fc40.noarch 10/13 Installing : python3-chardet-5.2.0-1.fc40.noarch 11/13 Installing : tox-4.11.1-1.fc40.noarch 12/13 Installing : python3-tox-current-env-0.0.11-5.fc39.noarch 13/13 Running scriptlet: python3-tox-current-env-0.0.11-5.fc39.noarch 13/13 Installed: python-setuptools-wheel-68.2.2-1.fc40.noarch python-wheel-wheel-1:0.41.2-1.fc40.noarch python3-cachetools-5.3.2-1.fc40.noarch python3-chardet-5.2.0-1.fc40.noarch python3-colorama-0.4.6-5.fc40.noarch python3-distlib-0.3.7-1.fc40.noarch python3-filelock-3.12.2-1.fc39.noarch python3-platformdirs-3.9.1-2.fc39.noarch python3-pluggy-1.3.0-1.fc40.noarch python3-pyproject-api-1.6.1-1.fc40.noarch python3-tox-current-env-0.0.11-5.fc39.noarch python3-virtualenv-20.21.1-5.fc40.noarch tox-4.11.1-1.fc40.noarch Complete! Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.9zf3uz + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-mailman3-1.3.9 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-mailman3-1.3.9.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-mailman3-1.3.9 + rm -rf /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-django42.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-py312-no-assertEquals.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.4ym6wG + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + echo 'python3dist(wheel)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + RPM_TOXENV=py312 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.2.2) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) running egg_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling tox-current-env >= 0.0.6 from tox itself Requirement satisfied: tox-current-env >= 0.0.6 (installed: tox-current-env 0.0.11) py312: OK (0.01 seconds) congratulations :) (0.04 seconds) Handling tox from tox --print-deps-only: py312 Requirement satisfied: tox (installed: tox 4.11.1) Handling mailmanclient from tox --print-deps-only: py312 Requirement not satisfied: mailmanclient Handling pytest-django from tox --print-deps-only: py312 Requirement not satisfied: pytest-django running dist_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/django-mailman3-1.3.9/django_mailman3-1.3.9.dist-info' Handling django <4.3,>=3.2 from hook generated metadata: Requires-Dist (django-mailman3) Requirement not satisfied: django <4.3,>=3.2 Handling mailmanclient >=3.3.3 from hook generated metadata: Requires-Dist (django-mailman3) Requirement not satisfied: mailmanclient >=3.3.3 Handling django-allauth from hook generated metadata: Requires-Dist (django-mailman3) Requirement not satisfied: django-allauth Handling django-gravatar2 >=1.0.6 from hook generated metadata: Requires-Dist (django-mailman3) Requirement not satisfied: django-gravatar2 >=1.0.6 Handling pytz from hook generated metadata: Requires-Dist (django-mailman3) Requirement not satisfied: pytz + cat /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires + rm -rfv django_mailman3-1.3.9.dist-info/ removed 'django_mailman3-1.3.9.dist-info/COPYING.txt' removed 'django_mailman3-1.3.9.dist-info/METADATA' removed 'django_mailman3-1.3.9.dist-info/top_level.txt' removed directory 'django_mailman3-1.3.9.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 95 kB/s | 1.5 kB 00:00 fedora 111 kB/s | 20 kB 00:00 Package pyproject-rpm-macros-1.10.0-1.fc40.noarch is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package python3-packaging-23.2-2.fc40.noarch is already installed. Package python3-pip-23.2.1-1.fc39.noarch is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package tox-4.11.1-1.fc40.noarch is already installed. Package python3-tox-current-env-0.0.11-5.fc39.noarch is already installed. Package python3-wheel-1:0.41.2-1.fc40.noarch is already installed. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: python3-django noarch 4.2.6-1.fc40 fedora 5.6 M python3-django-allauth noarch 0.54.0-1.fc39 fedora 1.3 M python3-django-gravatar2 noarch 1.4.4-7.fc39 fedora 30 k python3-mailmanclient noarch 3.3.3-8.fc39 fedora 173 k python3-pytest-django noarch 4.1.0-10.fc39 fedora 52 k python3-pytz noarch 2023.3.post1-1.fc40 fedora 64 k Installing dependencies: python3-asgiref noarch 3.7.2-1.fc40 fedora 64 k python3-cffi x86_64 1.16.0-1.fc40 copr_base 296 k python3-charset-normalizer noarch 3.3.2-1.fc40 fedora 107 k python3-cryptography x86_64 41.0.5-1.fc40 fedora 1.2 M python3-defusedxml noarch 0.7.1-10.fc40 fedora 59 k python3-idna noarch 3.4-5.fc40 fedora 109 k python3-iniconfig noarch 1.1.1-14.fc39 fedora 18 k python3-jwt noarch 2.6.0-4.fc39 fedora 61 k python3-jwt+crypto noarch 2.6.0-4.fc39 fedora 8.9 k python3-oauthlib noarch 3.2.2-1.fc40 fedora 242 k python3-openid noarch 3.1.0-19.fc39 fedora 266 k python3-ply noarch 3.11-20.fc39 fedora 135 k python3-pycparser noarch 2.20-12.fc40 fedora 156 k python3-pytest noarch 7.4.3-1.fc40 copr_base 1.8 M python3-requests noarch 2.31.0-1.fc40 copr_base 142 k python3-requests-oauthlib noarch 1.3.1-6.fc39 fedora 57 k python3-sqlparse noarch 0.4.2-7.fc39 fedora 117 k python3-urllib3 noarch 1.26.18-1.fc40 fedora 274 k Transaction Summary ================================================================================ Install 24 Packages Total size: 12 M Total download size: 9.9 M Installed size: 53 M Downloading Packages: [SKIPPED] python3-pytest-7.4.3-1.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-requests-2.31.0-1.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-charset-normalizer-3.3.2-1.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-idna-3.4-5.fc40.noarch.rpm: Already downloaded [SKIPPED] python3-iniconfig-1.1.1-14.fc39.noarch.rpm: Already downloaded [SKIPPED] python3-urllib3-1.26.18-1.fc40.noarch.rpm: Already downloaded (7/24): python3-cffi-1.16.0-1.fc40.x86_64.rpm 15 MB/s | 296 kB 00:00 (8/24): python3-asgiref-3.7.2-1.fc40.noarch.rpm 179 kB/s | 64 kB 00:00 (9/24): python3-defusedxml-0.7.1-10.fc40.noarch 169 kB/s | 59 kB 00:00 (10/24): python3-cryptography-41.0.5-1.fc40.x86 1.9 MB/s | 1.2 MB 00:00 (11/24): python3-django-gravatar2-1.4.4-7.fc39. 162 kB/s | 30 kB 00:00 (12/24): python3-jwt+crypto-2.6.0-4.fc39.noarch 42 kB/s | 8.9 kB 00:00 (13/24): python3-jwt-2.6.0-4.fc39.noarch.rpm 370 kB/s | 61 kB 00:00 (14/24): python3-django-4.2.6-1.fc40.noarch.rpm 6.4 MB/s | 5.6 MB 00:00 (15/24): python3-django-allauth-0.54.0-1.fc39.n 1.4 MB/s | 1.3 MB 00:00 (16/24): python3-mailmanclient-3.3.3-8.fc39.noa 225 kB/s | 173 kB 00:00 (17/24): python3-oauthlib-3.2.2-1.fc40.noarch.r 264 kB/s | 242 kB 00:00 (18/24): python3-openid-3.1.0-19.fc39.noarch.rp 307 kB/s | 266 kB 00:00 (19/24): python3-ply-3.11-20.fc39.noarch.rpm 791 kB/s | 135 kB 00:00 (20/24): python3-pycparser-2.20-12.fc40.noarch. 2.3 MB/s | 156 kB 00:00 (21/24): python3-pytest-django-4.1.0-10.fc39.no 161 kB/s | 52 kB 00:00 (22/24): python3-pytz-2023.3.post1-1.fc40.noarc 201 kB/s | 64 kB 00:00 (23/24): python3-requests-oauthlib-1.3.1-6.fc39 192 kB/s | 57 kB 00:00 (24/24): python3-sqlparse-0.4.2-7.fc39.noarch.r 482 kB/s | 117 kB 00:00 -------------------------------------------------------------------------------- Total 3.2 MB/s | 9.9 MB 00:03 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python3-idna-3.4-5.fc40.noarch 1/24 Installing : python3-urllib3-1.26.18-1.fc40.noarch 2/24 Installing : python3-sqlparse-0.4.2-7.fc39.noarch 3/24 Installing : python3-ply-3.11-20.fc39.noarch 4/24 Installing : python3-pycparser-2.20-12.fc40.noarch 5/24 Installing : python3-cffi-1.16.0-1.fc40.x86_64 6/24 Installing : python3-cryptography-41.0.5-1.fc40.x86_64 7/24 Installing : python3-jwt-2.6.0-4.fc39.noarch 8/24 Installing : python3-jwt+crypto-2.6.0-4.fc39.noarch 9/24 Installing : python3-oauthlib-3.2.2-1.fc40.noarch 10/24 Installing : python3-iniconfig-1.1.1-14.fc39.noarch 11/24 Installing : python3-pytest-7.4.3-1.fc40.noarch 12/24 Installing : python3-defusedxml-0.7.1-10.fc40.noarch 13/24 Installing : python3-openid-3.1.0-19.fc39.noarch 14/24 Installing : python3-charset-normalizer-3.3.2-1.fc40.noarch 15/24 Installing : python3-requests-2.31.0-1.fc40.noarch 16/24 Installing : python3-requests-oauthlib-1.3.1-6.fc39.noarch 17/24 Installing : python3-asgiref-3.7.2-1.fc40.noarch 18/24 Installing : python3-django-4.2.6-1.fc40.noarch 19/24 Installing : python3-django-allauth-0.54.0-1.fc39.noarch 20/24 Installing : python3-mailmanclient-3.3.3-8.fc39.noarch 21/24 Installing : python3-pytest-django-4.1.0-10.fc39.noarch 22/24 Installing : python3-pytz-2023.3.post1-1.fc40.noarch 23/24 Installing : python3-django-gravatar2-1.4.4-7.fc39.noarch 24/24 Running scriptlet: python3-django-gravatar2-1.4.4-7.fc39.noarch 24/24 Installed: python3-asgiref-3.7.2-1.fc40.noarch python3-cffi-1.16.0-1.fc40.x86_64 python3-charset-normalizer-3.3.2-1.fc40.noarch python3-cryptography-41.0.5-1.fc40.x86_64 python3-defusedxml-0.7.1-10.fc40.noarch python3-django-4.2.6-1.fc40.noarch python3-django-allauth-0.54.0-1.fc39.noarch python3-django-gravatar2-1.4.4-7.fc39.noarch python3-idna-3.4-5.fc40.noarch python3-iniconfig-1.1.1-14.fc39.noarch python3-jwt-2.6.0-4.fc39.noarch python3-jwt+crypto-2.6.0-4.fc39.noarch python3-mailmanclient-3.3.3-8.fc39.noarch python3-oauthlib-3.2.2-1.fc40.noarch python3-openid-3.1.0-19.fc39.noarch python3-ply-3.11-20.fc39.noarch python3-pycparser-2.20-12.fc40.noarch python3-pytest-7.4.3-1.fc40.noarch python3-pytest-django-4.1.0-10.fc39.noarch python3-pytz-2023.3.post1-1.fc40.noarch python3-requests-2.31.0-1.fc40.noarch python3-requests-oauthlib-1.3.1-6.fc39.noarch python3-sqlparse-0.4.2-7.fc39.noarch python3-urllib3-1.26.18-1.fc40.noarch Complete! Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.KUyE2X + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-mailman3-1.3.9 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-mailman3-1.3.9.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-mailman3-1.3.9 + rm -rf /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-django42.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/django-mailman3-py312-no-assertEquals.diff + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.oTBZ3r + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + echo 'python3dist(wheel)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + RPM_TOXENV=py312 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.2.2) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) running egg_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling tox-current-env >= 0.0.6 from tox itself Requirement satisfied: tox-current-env >= 0.0.6 (installed: tox-current-env 0.0.11) py312: OK (0.01 seconds) congratulations :) (0.04 seconds) Handling tox from tox --print-deps-only: py312 Requirement satisfied: tox (installed: tox 4.11.1) Handling mailmanclient from tox --print-deps-only: py312 Requirement satisfied: mailmanclient (installed: mailmanclient 3.3.3) Handling pytest-django from tox --print-deps-only: py312 Requirement satisfied: pytest-django (installed: pytest-django 4.1.0) running dist_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/django-mailman3-1.3.9/django_mailman3-1.3.9.dist-info' Handling django <4.3,>=3.2 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django <4.3,>=3.2 (installed: django 4.2.6) Handling mailmanclient >=3.3.3 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: mailmanclient >=3.3.3 (installed: mailmanclient 3.3.3) Handling django-allauth from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django-allauth (installed: django-allauth 0.54.0) Handling django-gravatar2 >=1.0.6 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django-gravatar2 >=1.0.6 (installed: django-gravatar2 1.4.4) Handling pytz from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: pytz (installed: pytz 2023.3.post1) + cat /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires + rm -rfv django_mailman3-1.3.9.dist-info/ removed 'django_mailman3-1.3.9.dist-info/COPYING.txt' removed 'django_mailman3-1.3.9.dist-info/METADATA' removed 'django_mailman3-1.3.9.dist-info/top_level.txt' removed directory 'django_mailman3-1.3.9.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires No matches found for the following disable plugin patterns: local, spacewalk, versionlock Copr repository 11 kB/s | 1.5 kB 00:00 fedora 302 kB/s | 20 kB 00:00 Package python3-django-4.2.6-1.fc40.noarch is already installed. Package pyproject-rpm-macros-1.10.0-1.fc40.noarch is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-devel-3.12.0-2.fc40.x86_64 is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package python3-django-allauth-0.54.0-1.fc39.noarch is already installed. Package python3-django-gravatar2-1.4.4-7.fc39.noarch is already installed. Package python3-mailmanclient-3.3.3-8.fc39.noarch is already installed. Package python3-mailmanclient-3.3.3-8.fc39.noarch is already installed. Package python3-packaging-23.2-2.fc40.noarch is already installed. Package python3-pip-23.2.1-1.fc39.noarch is already installed. Package python3-pytest-django-4.1.0-10.fc39.noarch is already installed. Package python3-pytz-2023.3.post1-1.fc40.noarch is already installed. Package python3-setuptools-68.2.2-1.fc40.noarch is already installed. Package tox-4.11.1-1.fc40.noarch is already installed. Package python3-tox-current-env-0.0.11-5.fc39.noarch is already installed. Package python3-wheel-1:0.41.2-1.fc40.noarch is already installed. Dependencies resolved. Nothing to do. Complete! Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1689897600 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.3xP02y + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + echo 'python3dist(wheel)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + RPM_TOXENV=py312 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.2.2) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) running egg_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling tox-current-env >= 0.0.6 from tox itself Requirement satisfied: tox-current-env >= 0.0.6 (installed: tox-current-env 0.0.11) py312: OK (0.01 seconds) congratulations :) (0.04 seconds) Handling tox from tox --print-deps-only: py312 Requirement satisfied: tox (installed: tox 4.11.1) Handling mailmanclient from tox --print-deps-only: py312 Requirement satisfied: mailmanclient (installed: mailmanclient 3.3.3) Handling pytest-django from tox --print-deps-only: py312 Requirement satisfied: pytest-django (installed: pytest-django 4.1.0) running dist_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/django-mailman3-1.3.9/django_mailman3-1.3.9.dist-info' Handling django <4.3,>=3.2 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django <4.3,>=3.2 (installed: django 4.2.6) Handling mailmanclient >=3.3.3 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: mailmanclient >=3.3.3 (installed: mailmanclient 3.3.3) Handling django-allauth from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django-allauth (installed: django-allauth 0.54.0) Handling django-gravatar2 >=1.0.6 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django-gravatar2 >=1.0.6 (installed: django-gravatar2 1.4.4) Handling pytz from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: pytz (installed: pytz 2023.3.post1) + cat /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-buildrequires + rm -rfv django_mailman3-1.3.9.dist-info/ removed 'django_mailman3-1.3.9.dist-info/COPYING.txt' removed 'django_mailman3-1.3.9.dist-info/METADATA' removed 'django_mailman3-1.3.9.dist-info/top_level.txt' removed directory 'django_mailman3-1.3.9.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.UK4VpJ + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -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-mailman3-1.3.9 + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir Processing /builddir/build/BUILD/django-mailman3-1.3.9 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) running dist_info creating /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info writing /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/PKG-INFO writing dependency_links to /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/dependency_links.txt writing requirements to /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/requires.txt writing top-level names to /builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/top_level.txt writing manifest file '/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/SOURCES.txt' reading manifest file '/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file '/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-modern-metadata-rl2nuv37/django_mailman3-1.3.9.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: django-mailman3 Building wheel for django-mailman3 (pyproject.toml): started Running command Building wheel for django-mailman3 (pyproject.toml) running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/django_mailman3 copying django_mailman3/urls.py -> build/lib/django_mailman3 copying django_mailman3/signals.py -> build/lib/django_mailman3 copying django_mailman3/models.py -> build/lib/django_mailman3 copying django_mailman3/forms.py -> build/lib/django_mailman3 copying django_mailman3/context_processors.py -> build/lib/django_mailman3 copying django_mailman3/apps.py -> build/lib/django_mailman3 copying django_mailman3/admin.py -> build/lib/django_mailman3 copying django_mailman3/__init__.py -> build/lib/django_mailman3 creating build/lib/django_mailman3/views copying django_mailman3/views/user_adapter.py -> build/lib/django_mailman3/views copying django_mailman3/views/profile.py -> build/lib/django_mailman3/views copying django_mailman3/views/__init__.py -> build/lib/django_mailman3/views creating build/lib/django_mailman3/tests copying django_mailman3/tests/test_delete_account.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/utils.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/urls_test.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_view_profile.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_signals.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_scrub.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_paginator.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_middlewares.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_mailman.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_lib_user.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_lib_auth_fedora_provider.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_forms.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_context_processors.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_bootstrap_tags.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/settings_test.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/__init__.py -> build/lib/django_mailman3/tests creating build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/pagination.py -> build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/d_gravatar.py -> build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/bootstrap_tags.py -> build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/__init__.py -> build/lib/django_mailman3/templatetags creating build/lib/django_mailman3/migrations copying django_mailman3/migrations/__init__.py -> build/lib/django_mailman3/migrations copying django_mailman3/migrations/0002_maildomain.py -> build/lib/django_mailman3/migrations copying django_mailman3/migrations/0001_initial.py -> build/lib/django_mailman3/migrations creating build/lib/django_mailman3/middleware copying django_mailman3/middleware/__init__.py -> build/lib/django_mailman3/middleware creating build/lib/django_mailman3/lib copying django_mailman3/lib/user.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/scrub.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/paginator.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/mailman.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/__init__.py -> build/lib/django_mailman3/lib creating build/lib/django_mailman3/lib/auth copying django_mailman3/lib/auth/__init__.py -> build/lib/django_mailman3/lib/auth creating build/lib/django_mailman3/lib/auth/fedora copying django_mailman3/lib/auth/fedora/views.py -> build/lib/django_mailman3/lib/auth/fedora copying django_mailman3/lib/auth/fedora/urls.py -> build/lib/django_mailman3/lib/auth/fedora copying django_mailman3/lib/auth/fedora/provider.py -> build/lib/django_mailman3/lib/auth/fedora copying django_mailman3/lib/auth/fedora/__init__.py -> build/lib/django_mailman3/lib/auth/fedora running egg_info writing django_mailman3.egg-info/PKG-INFO writing dependency_links to django_mailman3.egg-info/dependency_links.txt writing requirements to django_mailman3.egg-info/requires.txt writing top-level names to django_mailman3.egg-info/top_level.txt reading manifest file 'django_mailman3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txtl' under directory 'django_mailman3' adding license file 'COPYING.txt' writing manifest file 'django_mailman3.egg-info/SOURCES.txt' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.am.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.am.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.am.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.an.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.an.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.an.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.an.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.an.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.bem.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.bem.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.bem.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.bem.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.bem.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.bo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.bo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.bo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.bo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.bo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale' to be distributed and are already explicitly excluding 'django_mailman3.locale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ce.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ce.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.ce.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.ce.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ce.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.co.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.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_mailman3.locale.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_mailman3.locale.co.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.co.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.crh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.crh.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.crh.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.crh.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.crh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.cv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.cv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.cv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.cv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.cv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.en_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.en_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_mailman3.locale.en_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_mailman3.locale.en_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.en_CA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fil.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.fil.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.fil.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.fil.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fil.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.fo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.fo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.fo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fr_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.fr_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_mailman3.locale.fr_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_mailman3.locale.fr_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fr_CA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.frp.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.frp.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.frp.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.frp.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.frp.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.gu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.gu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.gu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ht.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ht.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.ht.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.ht.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ht.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.kl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.kl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.kl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.kl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.kl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ku.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ku.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.ku.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.ku.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ku.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.kw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.kw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.kw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.kw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.kw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.la.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.la.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.la.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.la.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.la.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.lo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.lo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.lo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.lo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.lo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.mg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.mg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.mg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.mg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.mg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.mhr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.mhr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.mhr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.mhr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.mhr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.mi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.mi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.mi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.mi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.mi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.nb_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.nb_NO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.nb_NO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.nb_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.nb_NO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.nn_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.nn_NO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.nn_NO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.nn_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.nn_NO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.oc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.oc.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.oc.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.oc.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.oc.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ps.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ps.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.ps.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.ps.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ps.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.sa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.sa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.sa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.sc.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.sc.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.sc.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sc.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.sd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.sd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.sd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.se.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.se.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.se.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.se.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.se.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.shn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.shn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.shn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.shn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.shn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.si.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.si.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.si.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.si.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.si.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.szl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.szl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.szl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.szl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.szl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ti.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ti.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.ti.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.ti.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ti.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.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_mailman3.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_mailman3.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.wae.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.wae.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.wae.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.wae.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.wae.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.zh_HK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.zh_HK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.zh_HK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.zh_HK.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.zh_HK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.static' to be distributed and are already explicitly excluding 'django_mailman3.static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.account' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.account' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.account' to be distributed and are already explicitly excluding 'django_mailman3.templates.account' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.django_mailman3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.django_mailman3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.django_mailman3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.django_mailman3' to be distributed and are already explicitly excluding 'django_mailman3.templates.django_mailman3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.django_mailman3.bootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.django_mailman3.bootstrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.django_mailman3.bootstrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.django_mailman3.bootstrap' to be distributed and are already explicitly excluding 'django_mailman3.templates.django_mailman3.bootstrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.django_mailman3.paginator' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.django_mailman3.paginator' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.django_mailman3.paginator' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.django_mailman3.paginator' to be distributed and are already explicitly excluding 'django_mailman3.templates.django_mailman3.paginator' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.django_mailman3.profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.django_mailman3.profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.django_mailman3.profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.django_mailman3.profile' to be distributed and are already explicitly excluding 'django_mailman3.templates.django_mailman3.profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.openid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.openid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.openid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.openid' to be distributed and are already explicitly excluding 'django_mailman3.templates.openid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.socialaccount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.socialaccount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.socialaccount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.socialaccount' to be distributed and are already explicitly excluding 'django_mailman3.templates.socialaccount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.templates.socialaccount.snippets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.templates.socialaccount.snippets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.templates.socialaccount.snippets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.templates.socialaccount.snippets' to be distributed and are already explicitly excluding 'django_mailman3.templates.socialaccount.snippets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'django_mailman3.tests.testdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.tests.testdata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_mailman3.tests.testdata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_mailman3.tests.testdata' to be distributed and are already explicitly excluding 'django_mailman3.tests.testdata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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_mailman3/locale creating build/lib/django_mailman3/locale/af creating build/lib/django_mailman3/locale/af/LC_MESSAGES copying django_mailman3/locale/af/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/af/LC_MESSAGES creating build/lib/django_mailman3/locale/am creating build/lib/django_mailman3/locale/am/LC_MESSAGES copying django_mailman3/locale/am/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/am/LC_MESSAGES creating build/lib/django_mailman3/locale/an creating build/lib/django_mailman3/locale/an/LC_MESSAGES copying django_mailman3/locale/an/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/an/LC_MESSAGES creating build/lib/django_mailman3/locale/ar creating build/lib/django_mailman3/locale/ar/LC_MESSAGES copying django_mailman3/locale/ar/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ar/LC_MESSAGES creating build/lib/django_mailman3/locale/ast creating build/lib/django_mailman3/locale/ast/LC_MESSAGES copying django_mailman3/locale/ast/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ast/LC_MESSAGES creating build/lib/django_mailman3/locale/az creating build/lib/django_mailman3/locale/az/LC_MESSAGES copying django_mailman3/locale/az/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/az/LC_MESSAGES creating build/lib/django_mailman3/locale/be creating build/lib/django_mailman3/locale/be/LC_MESSAGES copying django_mailman3/locale/be/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/be/LC_MESSAGES creating build/lib/django_mailman3/locale/bem creating build/lib/django_mailman3/locale/bem/LC_MESSAGES copying django_mailman3/locale/bem/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/bem/LC_MESSAGES creating build/lib/django_mailman3/locale/bg creating build/lib/django_mailman3/locale/bg/LC_MESSAGES copying django_mailman3/locale/bg/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/bg/LC_MESSAGES creating build/lib/django_mailman3/locale/bn creating build/lib/django_mailman3/locale/bn/LC_MESSAGES copying django_mailman3/locale/bn/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/bn/LC_MESSAGES creating build/lib/django_mailman3/locale/bo creating build/lib/django_mailman3/locale/bo/LC_MESSAGES copying django_mailman3/locale/bo/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/bo/LC_MESSAGES creating build/lib/django_mailman3/locale/br creating build/lib/django_mailman3/locale/br/LC_MESSAGES copying django_mailman3/locale/br/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/br/LC_MESSAGES creating build/lib/django_mailman3/locale/bs creating build/lib/django_mailman3/locale/bs/LC_MESSAGES copying django_mailman3/locale/bs/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/bs/LC_MESSAGES creating build/lib/django_mailman3/locale/ca creating build/lib/django_mailman3/locale/ca/LC_MESSAGES copying django_mailman3/locale/ca/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ca/LC_MESSAGES creating build/lib/django_mailman3/locale/ca@valencia creating build/lib/django_mailman3/locale/ca@valencia/LC_MESSAGES copying django_mailman3/locale/ca@valencia/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ca@valencia/LC_MESSAGES creating build/lib/django_mailman3/locale/ce creating build/lib/django_mailman3/locale/ce/LC_MESSAGES copying django_mailman3/locale/ce/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ce/LC_MESSAGES creating build/lib/django_mailman3/locale/ckb creating build/lib/django_mailman3/locale/ckb/LC_MESSAGES copying django_mailman3/locale/ckb/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ckb/LC_MESSAGES creating build/lib/django_mailman3/locale/co creating build/lib/django_mailman3/locale/co/LC_MESSAGES copying django_mailman3/locale/co/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/co/LC_MESSAGES creating build/lib/django_mailman3/locale/crh creating build/lib/django_mailman3/locale/crh/LC_MESSAGES copying django_mailman3/locale/crh/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/crh/LC_MESSAGES creating build/lib/django_mailman3/locale/cs creating build/lib/django_mailman3/locale/cs/LC_MESSAGES copying django_mailman3/locale/cs/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/cs/LC_MESSAGES creating build/lib/django_mailman3/locale/cv creating build/lib/django_mailman3/locale/cv/LC_MESSAGES copying django_mailman3/locale/cv/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/cv/LC_MESSAGES creating build/lib/django_mailman3/locale/cy creating build/lib/django_mailman3/locale/cy/LC_MESSAGES copying django_mailman3/locale/cy/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/cy/LC_MESSAGES creating build/lib/django_mailman3/locale/da creating build/lib/django_mailman3/locale/da/LC_MESSAGES copying django_mailman3/locale/da/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/da/LC_MESSAGES creating build/lib/django_mailman3/locale/de creating build/lib/django_mailman3/locale/de/LC_MESSAGES copying django_mailman3/locale/de/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/de/LC_MESSAGES creating build/lib/django_mailman3/locale/el creating build/lib/django_mailman3/locale/el/LC_MESSAGES copying django_mailman3/locale/el/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/el/LC_MESSAGES creating build/lib/django_mailman3/locale/en_AU creating build/lib/django_mailman3/locale/en_AU/LC_MESSAGES copying django_mailman3/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/en_AU/LC_MESSAGES creating build/lib/django_mailman3/locale/en_CA creating build/lib/django_mailman3/locale/en_CA/LC_MESSAGES copying django_mailman3/locale/en_CA/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/en_CA/LC_MESSAGES creating build/lib/django_mailman3/locale/en_GB creating build/lib/django_mailman3/locale/en_GB/LC_MESSAGES copying django_mailman3/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/en_GB/LC_MESSAGES creating build/lib/django_mailman3/locale/eo creating build/lib/django_mailman3/locale/eo/LC_MESSAGES copying django_mailman3/locale/eo/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/eo/LC_MESSAGES creating build/lib/django_mailman3/locale/es creating build/lib/django_mailman3/locale/es/LC_MESSAGES copying django_mailman3/locale/es/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/es/LC_MESSAGES creating build/lib/django_mailman3/locale/et creating build/lib/django_mailman3/locale/et/LC_MESSAGES copying django_mailman3/locale/et/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/et/LC_MESSAGES creating build/lib/django_mailman3/locale/eu creating build/lib/django_mailman3/locale/eu/LC_MESSAGES copying django_mailman3/locale/eu/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/eu/LC_MESSAGES creating build/lib/django_mailman3/locale/fa creating build/lib/django_mailman3/locale/fa/LC_MESSAGES copying django_mailman3/locale/fa/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fa/LC_MESSAGES creating build/lib/django_mailman3/locale/fi creating build/lib/django_mailman3/locale/fi/LC_MESSAGES copying django_mailman3/locale/fi/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fi/LC_MESSAGES creating build/lib/django_mailman3/locale/fil creating build/lib/django_mailman3/locale/fil/LC_MESSAGES copying django_mailman3/locale/fil/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fil/LC_MESSAGES creating build/lib/django_mailman3/locale/fo creating build/lib/django_mailman3/locale/fo/LC_MESSAGES copying django_mailman3/locale/fo/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fo/LC_MESSAGES creating build/lib/django_mailman3/locale/fr creating build/lib/django_mailman3/locale/fr/LC_MESSAGES copying django_mailman3/locale/fr/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fr/LC_MESSAGES creating build/lib/django_mailman3/locale/fr_CA creating build/lib/django_mailman3/locale/fr_CA/LC_MESSAGES copying django_mailman3/locale/fr_CA/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fr_CA/LC_MESSAGES creating build/lib/django_mailman3/locale/frp creating build/lib/django_mailman3/locale/frp/LC_MESSAGES copying django_mailman3/locale/frp/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/frp/LC_MESSAGES creating build/lib/django_mailman3/locale/fy creating build/lib/django_mailman3/locale/fy/LC_MESSAGES copying django_mailman3/locale/fy/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/fy/LC_MESSAGES creating build/lib/django_mailman3/locale/ga creating build/lib/django_mailman3/locale/ga/LC_MESSAGES copying django_mailman3/locale/ga/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ga/LC_MESSAGES creating build/lib/django_mailman3/locale/gd creating build/lib/django_mailman3/locale/gd/LC_MESSAGES copying django_mailman3/locale/gd/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/gd/LC_MESSAGES creating build/lib/django_mailman3/locale/gl creating build/lib/django_mailman3/locale/gl/LC_MESSAGES copying django_mailman3/locale/gl/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/gl/LC_MESSAGES creating build/lib/django_mailman3/locale/gu creating build/lib/django_mailman3/locale/gu/LC_MESSAGES copying django_mailman3/locale/gu/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/gu/LC_MESSAGES creating build/lib/django_mailman3/locale/he creating build/lib/django_mailman3/locale/he/LC_MESSAGES copying django_mailman3/locale/he/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/he/LC_MESSAGES creating build/lib/django_mailman3/locale/hi creating build/lib/django_mailman3/locale/hi/LC_MESSAGES copying django_mailman3/locale/hi/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/hi/LC_MESSAGES creating build/lib/django_mailman3/locale/hr creating build/lib/django_mailman3/locale/hr/LC_MESSAGES copying django_mailman3/locale/hr/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/hr/LC_MESSAGES creating build/lib/django_mailman3/locale/ht creating build/lib/django_mailman3/locale/ht/LC_MESSAGES copying django_mailman3/locale/ht/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ht/LC_MESSAGES creating build/lib/django_mailman3/locale/hu creating build/lib/django_mailman3/locale/hu/LC_MESSAGES copying django_mailman3/locale/hu/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/hu/LC_MESSAGES creating build/lib/django_mailman3/locale/hy creating build/lib/django_mailman3/locale/hy/LC_MESSAGES copying django_mailman3/locale/hy/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/hy/LC_MESSAGES creating build/lib/django_mailman3/locale/ia creating build/lib/django_mailman3/locale/ia/LC_MESSAGES copying django_mailman3/locale/ia/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ia/LC_MESSAGES creating build/lib/django_mailman3/locale/id creating build/lib/django_mailman3/locale/id/LC_MESSAGES copying django_mailman3/locale/id/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/id/LC_MESSAGES creating build/lib/django_mailman3/locale/is creating build/lib/django_mailman3/locale/is/LC_MESSAGES copying django_mailman3/locale/is/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/is/LC_MESSAGES creating build/lib/django_mailman3/locale/it creating build/lib/django_mailman3/locale/it/LC_MESSAGES copying django_mailman3/locale/it/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/it/LC_MESSAGES creating build/lib/django_mailman3/locale/ja creating build/lib/django_mailman3/locale/ja/LC_MESSAGES copying django_mailman3/locale/ja/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ja/LC_MESSAGES creating build/lib/django_mailman3/locale/ka creating build/lib/django_mailman3/locale/ka/LC_MESSAGES copying django_mailman3/locale/ka/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ka/LC_MESSAGES creating build/lib/django_mailman3/locale/kk creating build/lib/django_mailman3/locale/kk/LC_MESSAGES copying django_mailman3/locale/kk/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/kk/LC_MESSAGES creating build/lib/django_mailman3/locale/kl creating build/lib/django_mailman3/locale/kl/LC_MESSAGES copying django_mailman3/locale/kl/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/kl/LC_MESSAGES creating build/lib/django_mailman3/locale/km creating build/lib/django_mailman3/locale/km/LC_MESSAGES copying django_mailman3/locale/km/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/km/LC_MESSAGES creating build/lib/django_mailman3/locale/kn creating build/lib/django_mailman3/locale/kn/LC_MESSAGES copying django_mailman3/locale/kn/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/kn/LC_MESSAGES creating build/lib/django_mailman3/locale/ko creating build/lib/django_mailman3/locale/ko/LC_MESSAGES copying django_mailman3/locale/ko/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ko/LC_MESSAGES creating build/lib/django_mailman3/locale/ku creating build/lib/django_mailman3/locale/ku/LC_MESSAGES copying django_mailman3/locale/ku/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ku/LC_MESSAGES creating build/lib/django_mailman3/locale/kw creating build/lib/django_mailman3/locale/kw/LC_MESSAGES copying django_mailman3/locale/kw/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/kw/LC_MESSAGES creating build/lib/django_mailman3/locale/ky creating build/lib/django_mailman3/locale/ky/LC_MESSAGES copying django_mailman3/locale/ky/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ky/LC_MESSAGES creating build/lib/django_mailman3/locale/la creating build/lib/django_mailman3/locale/la/LC_MESSAGES copying django_mailman3/locale/la/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/la/LC_MESSAGES creating build/lib/django_mailman3/locale/lb creating build/lib/django_mailman3/locale/lb/LC_MESSAGES copying django_mailman3/locale/lb/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/lb/LC_MESSAGES creating build/lib/django_mailman3/locale/lo creating build/lib/django_mailman3/locale/lo/LC_MESSAGES copying django_mailman3/locale/lo/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/lo/LC_MESSAGES creating build/lib/django_mailman3/locale/lt creating build/lib/django_mailman3/locale/lt/LC_MESSAGES copying django_mailman3/locale/lt/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/lt/LC_MESSAGES creating build/lib/django_mailman3/locale/lv creating build/lib/django_mailman3/locale/lv/LC_MESSAGES copying django_mailman3/locale/lv/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/lv/LC_MESSAGES creating build/lib/django_mailman3/locale/mg creating build/lib/django_mailman3/locale/mg/LC_MESSAGES copying django_mailman3/locale/mg/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/mg/LC_MESSAGES creating build/lib/django_mailman3/locale/mhr creating build/lib/django_mailman3/locale/mhr/LC_MESSAGES copying django_mailman3/locale/mhr/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/mhr/LC_MESSAGES creating build/lib/django_mailman3/locale/mi creating build/lib/django_mailman3/locale/mi/LC_MESSAGES copying django_mailman3/locale/mi/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/mi/LC_MESSAGES creating build/lib/django_mailman3/locale/ml creating build/lib/django_mailman3/locale/ml/LC_MESSAGES copying django_mailman3/locale/ml/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ml/LC_MESSAGES creating build/lib/django_mailman3/locale/mr creating build/lib/django_mailman3/locale/mr/LC_MESSAGES copying django_mailman3/locale/mr/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/mr/LC_MESSAGES creating build/lib/django_mailman3/locale/ms creating build/lib/django_mailman3/locale/ms/LC_MESSAGES copying django_mailman3/locale/ms/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ms/LC_MESSAGES creating build/lib/django_mailman3/locale/my creating build/lib/django_mailman3/locale/my/LC_MESSAGES copying django_mailman3/locale/my/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/my/LC_MESSAGES creating build/lib/django_mailman3/locale/nb_NO creating build/lib/django_mailman3/locale/nb_NO/LC_MESSAGES copying django_mailman3/locale/nb_NO/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/nb_NO/LC_MESSAGES creating build/lib/django_mailman3/locale/ne creating build/lib/django_mailman3/locale/ne/LC_MESSAGES copying django_mailman3/locale/ne/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ne/LC_MESSAGES creating build/lib/django_mailman3/locale/nl creating build/lib/django_mailman3/locale/nl/LC_MESSAGES copying django_mailman3/locale/nl/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/nl/LC_MESSAGES creating build/lib/django_mailman3/locale/nn_NO creating build/lib/django_mailman3/locale/nn_NO/LC_MESSAGES copying django_mailman3/locale/nn_NO/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/nn_NO/LC_MESSAGES creating build/lib/django_mailman3/locale/oc creating build/lib/django_mailman3/locale/oc/LC_MESSAGES copying django_mailman3/locale/oc/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/oc/LC_MESSAGES creating build/lib/django_mailman3/locale/os creating build/lib/django_mailman3/locale/os/LC_MESSAGES copying django_mailman3/locale/os/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/os/LC_MESSAGES creating build/lib/django_mailman3/locale/pa creating build/lib/django_mailman3/locale/pa/LC_MESSAGES copying django_mailman3/locale/pa/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/pa/LC_MESSAGES creating build/lib/django_mailman3/locale/pl creating build/lib/django_mailman3/locale/pl/LC_MESSAGES copying django_mailman3/locale/pl/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/pl/LC_MESSAGES creating build/lib/django_mailman3/locale/ps creating build/lib/django_mailman3/locale/ps/LC_MESSAGES copying django_mailman3/locale/ps/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ps/LC_MESSAGES creating build/lib/django_mailman3/locale/pt creating build/lib/django_mailman3/locale/pt/LC_MESSAGES copying django_mailman3/locale/pt/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/pt/LC_MESSAGES creating build/lib/django_mailman3/locale/pt_BR creating build/lib/django_mailman3/locale/pt_BR/LC_MESSAGES copying django_mailman3/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/pt_BR/LC_MESSAGES creating build/lib/django_mailman3/locale/ro creating build/lib/django_mailman3/locale/ro/LC_MESSAGES copying django_mailman3/locale/ro/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ro/LC_MESSAGES creating build/lib/django_mailman3/locale/ru creating build/lib/django_mailman3/locale/ru/LC_MESSAGES copying django_mailman3/locale/ru/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ru/LC_MESSAGES creating build/lib/django_mailman3/locale/sa creating build/lib/django_mailman3/locale/sa/LC_MESSAGES copying django_mailman3/locale/sa/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sa/LC_MESSAGES creating build/lib/django_mailman3/locale/sc creating build/lib/django_mailman3/locale/sc/LC_MESSAGES copying django_mailman3/locale/sc/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sc/LC_MESSAGES creating build/lib/django_mailman3/locale/sd creating build/lib/django_mailman3/locale/sd/LC_MESSAGES copying django_mailman3/locale/sd/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sd/LC_MESSAGES creating build/lib/django_mailman3/locale/se creating build/lib/django_mailman3/locale/se/LC_MESSAGES copying django_mailman3/locale/se/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/se/LC_MESSAGES creating build/lib/django_mailman3/locale/shn creating build/lib/django_mailman3/locale/shn/LC_MESSAGES copying django_mailman3/locale/shn/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/shn/LC_MESSAGES creating build/lib/django_mailman3/locale/si creating build/lib/django_mailman3/locale/si/LC_MESSAGES copying django_mailman3/locale/si/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/si/LC_MESSAGES creating build/lib/django_mailman3/locale/sk creating build/lib/django_mailman3/locale/sk/LC_MESSAGES copying django_mailman3/locale/sk/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sk/LC_MESSAGES creating build/lib/django_mailman3/locale/sl creating build/lib/django_mailman3/locale/sl/LC_MESSAGES copying django_mailman3/locale/sl/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sl/LC_MESSAGES creating build/lib/django_mailman3/locale/sq creating build/lib/django_mailman3/locale/sq/LC_MESSAGES copying django_mailman3/locale/sq/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sq/LC_MESSAGES creating build/lib/django_mailman3/locale/sr creating build/lib/django_mailman3/locale/sr/LC_MESSAGES copying django_mailman3/locale/sr/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sr/LC_MESSAGES creating build/lib/django_mailman3/locale/sv creating build/lib/django_mailman3/locale/sv/LC_MESSAGES copying django_mailman3/locale/sv/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sv/LC_MESSAGES creating build/lib/django_mailman3/locale/sw creating build/lib/django_mailman3/locale/sw/LC_MESSAGES copying django_mailman3/locale/sw/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/sw/LC_MESSAGES creating build/lib/django_mailman3/locale/szl creating build/lib/django_mailman3/locale/szl/LC_MESSAGES copying django_mailman3/locale/szl/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/szl/LC_MESSAGES creating build/lib/django_mailman3/locale/ta creating build/lib/django_mailman3/locale/ta/LC_MESSAGES copying django_mailman3/locale/ta/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ta/LC_MESSAGES creating build/lib/django_mailman3/locale/te creating build/lib/django_mailman3/locale/te/LC_MESSAGES copying django_mailman3/locale/te/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/te/LC_MESSAGES creating build/lib/django_mailman3/locale/tg creating build/lib/django_mailman3/locale/tg/LC_MESSAGES copying django_mailman3/locale/tg/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/tg/LC_MESSAGES creating build/lib/django_mailman3/locale/th creating build/lib/django_mailman3/locale/th/LC_MESSAGES copying django_mailman3/locale/th/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/th/LC_MESSAGES creating build/lib/django_mailman3/locale/ti creating build/lib/django_mailman3/locale/ti/LC_MESSAGES copying django_mailman3/locale/ti/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ti/LC_MESSAGES creating build/lib/django_mailman3/locale/tr creating build/lib/django_mailman3/locale/tr/LC_MESSAGES copying django_mailman3/locale/tr/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/tr/LC_MESSAGES creating build/lib/django_mailman3/locale/ug creating build/lib/django_mailman3/locale/ug/LC_MESSAGES copying django_mailman3/locale/ug/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ug/LC_MESSAGES creating build/lib/django_mailman3/locale/uk creating build/lib/django_mailman3/locale/uk/LC_MESSAGES copying django_mailman3/locale/uk/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/uk/LC_MESSAGES creating build/lib/django_mailman3/locale/ur creating build/lib/django_mailman3/locale/ur/LC_MESSAGES copying django_mailman3/locale/ur/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ur/LC_MESSAGES creating build/lib/django_mailman3/locale/uz creating build/lib/django_mailman3/locale/uz/LC_MESSAGES copying django_mailman3/locale/uz/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/uz/LC_MESSAGES creating build/lib/django_mailman3/locale/vi creating build/lib/django_mailman3/locale/vi/LC_MESSAGES copying django_mailman3/locale/vi/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/vi/LC_MESSAGES creating build/lib/django_mailman3/locale/wae creating build/lib/django_mailman3/locale/wae/LC_MESSAGES copying django_mailman3/locale/wae/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/wae/LC_MESSAGES creating build/lib/django_mailman3/locale/zh_CN creating build/lib/django_mailman3/locale/zh_CN/LC_MESSAGES copying django_mailman3/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/zh_CN/LC_MESSAGES creating build/lib/django_mailman3/locale/zh_HK creating build/lib/django_mailman3/locale/zh_HK/LC_MESSAGES copying django_mailman3/locale/zh_HK/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/zh_HK/LC_MESSAGES creating build/lib/django_mailman3/locale/zh_TW creating build/lib/django_mailman3/locale/zh_TW/LC_MESSAGES copying django_mailman3/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/zh_TW/LC_MESSAGES creating build/lib/django_mailman3/static creating build/lib/django_mailman3/static/django-mailman3 creating build/lib/django_mailman3/static/django-mailman3/css copying django_mailman3/static/django-mailman3/css/main.css -> build/lib/django_mailman3/static/django-mailman3/css creating build/lib/django_mailman3/static/django-mailman3/img creating build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/facebook.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/fedora.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/github.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/gitlab.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/google.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/openid.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/stackexchange.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/stackoverflow.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/twitter.png -> build/lib/django_mailman3/static/django-mailman3/img/login copying django_mailman3/static/django-mailman3/img/login/yahoo.png -> build/lib/django_mailman3/static/django-mailman3/img/login creating build/lib/django_mailman3/static/django-mailman3/js copying django_mailman3/static/django-mailman3/js/main.js -> build/lib/django_mailman3/static/django-mailman3/js creating build/lib/django_mailman3/templates creating build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/email.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/email_confirm.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/login.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/logout.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/password_change.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/password_reset.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/password_reset_from_key.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/password_set.html -> build/lib/django_mailman3/templates/account copying django_mailman3/templates/account/signup.html -> build/lib/django_mailman3/templates/account creating build/lib/django_mailman3/templates/django_mailman3 copying django_mailman3/templates/django_mailman3/base.html -> build/lib/django_mailman3/templates/django_mailman3 copying django_mailman3/templates/django_mailman3/login_extra_post_providers.html -> build/lib/django_mailman3/templates/django_mailman3 copying django_mailman3/templates/django_mailman3/login_extra_top.html -> build/lib/django_mailman3/templates/django_mailman3 creating build/lib/django_mailman3/templates/django_mailman3/bootstrap copying django_mailman3/templates/django_mailman3/bootstrap/form-horizontal.html -> build/lib/django_mailman3/templates/django_mailman3/bootstrap copying django_mailman3/templates/django_mailman3/bootstrap/form.html -> build/lib/django_mailman3/templates/django_mailman3/bootstrap creating build/lib/django_mailman3/templates/django_mailman3/paginator copying django_mailman3/templates/django_mailman3/paginator/pagination.html -> build/lib/django_mailman3/templates/django_mailman3/paginator creating build/lib/django_mailman3/templates/django_mailman3/profile copying django_mailman3/templates/django_mailman3/profile/base.html -> build/lib/django_mailman3/templates/django_mailman3/profile copying django_mailman3/templates/django_mailman3/profile/delete_profile.html -> build/lib/django_mailman3/templates/django_mailman3/profile copying django_mailman3/templates/django_mailman3/profile/profile.html -> build/lib/django_mailman3/templates/django_mailman3/profile creating build/lib/django_mailman3/templates/openid copying django_mailman3/templates/openid/login.html -> build/lib/django_mailman3/templates/openid creating build/lib/django_mailman3/templates/socialaccount copying django_mailman3/templates/socialaccount/connections.html -> build/lib/django_mailman3/templates/socialaccount copying django_mailman3/templates/socialaccount/signup.html -> build/lib/django_mailman3/templates/socialaccount creating build/lib/django_mailman3/templates/socialaccount/snippets copying django_mailman3/templates/socialaccount/snippets/provider_list.html -> build/lib/django_mailman3/templates/socialaccount/snippets creating build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/attached_message.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/attachment-1.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/attachment-2.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/attachment-3.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/attachment-4.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/attachment-5.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/bad_charset.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/email-bad-filename.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/html-email-1.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/html-email-2.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/null_byte.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/null_byte_multipart.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/payload-iso8859.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/payload-unknown.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/payload-utf8.txt -> build/lib/django_mailman3/tests/testdata copying django_mailman3/tests/testdata/pipermail_nextpart.txt -> build/lib/django_mailman3/tests/testdata installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/django_mailman3 creating build/bdist.linux-x86_64/wheel/django_mailman3/templates creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/socialaccount creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/socialaccount/snippets copying build/lib/django_mailman3/templates/socialaccount/snippets/provider_list.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/socialaccount/snippets copying build/lib/django_mailman3/templates/socialaccount/signup.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/socialaccount copying build/lib/django_mailman3/templates/socialaccount/connections.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/socialaccount creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/openid copying build/lib/django_mailman3/templates/openid/login.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/openid creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3 creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/profile copying build/lib/django_mailman3/templates/django_mailman3/profile/profile.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/profile copying build/lib/django_mailman3/templates/django_mailman3/profile/delete_profile.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/profile copying build/lib/django_mailman3/templates/django_mailman3/profile/base.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/profile creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/paginator copying build/lib/django_mailman3/templates/django_mailman3/paginator/pagination.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/paginator creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/bootstrap copying build/lib/django_mailman3/templates/django_mailman3/bootstrap/form.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/bootstrap copying build/lib/django_mailman3/templates/django_mailman3/bootstrap/form-horizontal.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3/bootstrap copying build/lib/django_mailman3/templates/django_mailman3/login_extra_top.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3 copying build/lib/django_mailman3/templates/django_mailman3/login_extra_post_providers.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3 copying build/lib/django_mailman3/templates/django_mailman3/base.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/django_mailman3 creating build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/signup.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_set.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_reset_from_key.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_reset.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_change.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/logout.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/login.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/email_confirm.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/email.html -> build/bdist.linux-x86_64/wheel/django_mailman3/templates/account creating build/bdist.linux-x86_64/wheel/django_mailman3/static creating build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3 creating build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/js copying build/lib/django_mailman3/static/django-mailman3/js/main.js -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/js creating build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img creating build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/yahoo.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/twitter.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/stackoverflow.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/stackexchange.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/openid.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/google.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/gitlab.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/github.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/fedora.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/facebook.png -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/img/login creating build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/css copying build/lib/django_mailman3/static/django-mailman3/css/main.css -> build/bdist.linux-x86_64/wheel/django_mailman3/static/django-mailman3/css creating build/bdist.linux-x86_64/wheel/django_mailman3/locale creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_TW creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_TW/LC_MESSAGES copying build/lib/django_mailman3/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_TW/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_HK creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_HK/LC_MESSAGES copying build/lib/django_mailman3/locale/zh_HK/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_HK/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_CN creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_CN/LC_MESSAGES copying build/lib/django_mailman3/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/zh_CN/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/wae creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/wae/LC_MESSAGES copying build/lib/django_mailman3/locale/wae/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/wae/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/vi creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/vi/LC_MESSAGES copying build/lib/django_mailman3/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/uz creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/uz/LC_MESSAGES copying build/lib/django_mailman3/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ur creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ur/LC_MESSAGES copying build/lib/django_mailman3/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/uk creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/uk/LC_MESSAGES copying build/lib/django_mailman3/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ug creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ug/LC_MESSAGES copying build/lib/django_mailman3/locale/ug/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ug/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/tr creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/tr/LC_MESSAGES copying build/lib/django_mailman3/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ti creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ti/LC_MESSAGES copying build/lib/django_mailman3/locale/ti/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ti/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/th creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/th/LC_MESSAGES copying build/lib/django_mailman3/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/tg creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/tg/LC_MESSAGES copying build/lib/django_mailman3/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/te creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/te/LC_MESSAGES copying build/lib/django_mailman3/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ta creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ta/LC_MESSAGES copying build/lib/django_mailman3/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/szl creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/szl/LC_MESSAGES copying build/lib/django_mailman3/locale/szl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/szl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sw creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sw/LC_MESSAGES copying build/lib/django_mailman3/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sv creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sv/LC_MESSAGES copying build/lib/django_mailman3/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sr creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sr/LC_MESSAGES copying build/lib/django_mailman3/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sq creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sq/LC_MESSAGES copying build/lib/django_mailman3/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sl creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sl/LC_MESSAGES copying build/lib/django_mailman3/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sk creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sk/LC_MESSAGES copying build/lib/django_mailman3/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/si creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/si/LC_MESSAGES copying build/lib/django_mailman3/locale/si/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/si/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/shn creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/shn/LC_MESSAGES copying build/lib/django_mailman3/locale/shn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/shn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/se creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/se/LC_MESSAGES copying build/lib/django_mailman3/locale/se/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/se/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sd creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sd/LC_MESSAGES copying build/lib/django_mailman3/locale/sd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sc creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sc/LC_MESSAGES copying build/lib/django_mailman3/locale/sc/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sc/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sa creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/sa/LC_MESSAGES copying build/lib/django_mailman3/locale/sa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/sa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ru creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ru/LC_MESSAGES copying build/lib/django_mailman3/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ro creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ro/LC_MESSAGES copying build/lib/django_mailman3/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pt_BR/LC_MESSAGES copying build/lib/django_mailman3/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pt creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pt/LC_MESSAGES copying build/lib/django_mailman3/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ps creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ps/LC_MESSAGES copying build/lib/django_mailman3/locale/ps/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ps/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pl creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pl/LC_MESSAGES copying build/lib/django_mailman3/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pa creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/pa/LC_MESSAGES copying build/lib/django_mailman3/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/os creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/os/LC_MESSAGES copying build/lib/django_mailman3/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/oc creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/oc/LC_MESSAGES copying build/lib/django_mailman3/locale/oc/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/oc/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/nn_NO creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/nn_NO/LC_MESSAGES copying build/lib/django_mailman3/locale/nn_NO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/nn_NO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/nl creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/nl/LC_MESSAGES copying build/lib/django_mailman3/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ne creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ne/LC_MESSAGES copying build/lib/django_mailman3/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/nb_NO creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/nb_NO/LC_MESSAGES copying build/lib/django_mailman3/locale/nb_NO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/nb_NO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/my creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/my/LC_MESSAGES copying build/lib/django_mailman3/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ms creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ms/LC_MESSAGES copying build/lib/django_mailman3/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mr creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mr/LC_MESSAGES copying build/lib/django_mailman3/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ml creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ml/LC_MESSAGES copying build/lib/django_mailman3/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mi creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mi/LC_MESSAGES copying build/lib/django_mailman3/locale/mi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/mi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mhr creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mhr/LC_MESSAGES copying build/lib/django_mailman3/locale/mhr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/mhr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mg creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/mg/LC_MESSAGES copying build/lib/django_mailman3/locale/mg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/mg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lv creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lv/LC_MESSAGES copying build/lib/django_mailman3/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lt creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lt/LC_MESSAGES copying build/lib/django_mailman3/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lo creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lo/LC_MESSAGES copying build/lib/django_mailman3/locale/lo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/lo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lb creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/lb/LC_MESSAGES copying build/lib/django_mailman3/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/la creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/la/LC_MESSAGES copying build/lib/django_mailman3/locale/la/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/la/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ky creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ky/LC_MESSAGES copying build/lib/django_mailman3/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kw creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kw/LC_MESSAGES copying build/lib/django_mailman3/locale/kw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/kw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ku creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ku/LC_MESSAGES copying build/lib/django_mailman3/locale/ku/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ku/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ko creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ko/LC_MESSAGES copying build/lib/django_mailman3/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kn creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kn/LC_MESSAGES copying build/lib/django_mailman3/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/km creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/km/LC_MESSAGES copying build/lib/django_mailman3/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kl creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kl/LC_MESSAGES copying build/lib/django_mailman3/locale/kl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/kl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kk creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/kk/LC_MESSAGES copying build/lib/django_mailman3/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ka creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ka/LC_MESSAGES copying build/lib/django_mailman3/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ja creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ja/LC_MESSAGES copying build/lib/django_mailman3/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/it creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/it/LC_MESSAGES copying build/lib/django_mailman3/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/is creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/is/LC_MESSAGES copying build/lib/django_mailman3/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/id creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/id/LC_MESSAGES copying build/lib/django_mailman3/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ia creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ia/LC_MESSAGES copying build/lib/django_mailman3/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hy creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hy/LC_MESSAGES copying build/lib/django_mailman3/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hu creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hu/LC_MESSAGES copying build/lib/django_mailman3/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ht creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ht/LC_MESSAGES copying build/lib/django_mailman3/locale/ht/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ht/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hr creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hr/LC_MESSAGES copying build/lib/django_mailman3/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hi creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/hi/LC_MESSAGES copying build/lib/django_mailman3/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/he creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/he/LC_MESSAGES copying build/lib/django_mailman3/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/gu creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/gu/LC_MESSAGES copying build/lib/django_mailman3/locale/gu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/gu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/gl creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/gl/LC_MESSAGES copying build/lib/django_mailman3/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/gd creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/gd/LC_MESSAGES copying build/lib/django_mailman3/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ga creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ga/LC_MESSAGES copying build/lib/django_mailman3/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fy creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fy/LC_MESSAGES copying build/lib/django_mailman3/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/frp creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/frp/LC_MESSAGES copying build/lib/django_mailman3/locale/frp/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/frp/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fr_CA creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fr_CA/LC_MESSAGES copying build/lib/django_mailman3/locale/fr_CA/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fr_CA/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fr creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fr/LC_MESSAGES copying build/lib/django_mailman3/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fo creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fo/LC_MESSAGES copying build/lib/django_mailman3/locale/fo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fil creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fil/LC_MESSAGES copying build/lib/django_mailman3/locale/fil/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fil/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fi creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fi/LC_MESSAGES copying build/lib/django_mailman3/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fa creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/fa/LC_MESSAGES copying build/lib/django_mailman3/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/eu creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/eu/LC_MESSAGES copying build/lib/django_mailman3/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/et creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/et/LC_MESSAGES copying build/lib/django_mailman3/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/es creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/es/LC_MESSAGES copying build/lib/django_mailman3/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/eo creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/eo/LC_MESSAGES copying build/lib/django_mailman3/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_GB creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_GB/LC_MESSAGES copying build/lib/django_mailman3/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_CA creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_CA/LC_MESSAGES copying build/lib/django_mailman3/locale/en_CA/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_CA/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_AU creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_AU/LC_MESSAGES copying build/lib/django_mailman3/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/el creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/el/LC_MESSAGES copying build/lib/django_mailman3/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/de creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/de/LC_MESSAGES copying build/lib/django_mailman3/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/da creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/da/LC_MESSAGES copying build/lib/django_mailman3/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/cy creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/cy/LC_MESSAGES copying build/lib/django_mailman3/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/cv creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/cv/LC_MESSAGES copying build/lib/django_mailman3/locale/cv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/cv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/cs creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/cs/LC_MESSAGES copying build/lib/django_mailman3/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/crh creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/crh/LC_MESSAGES copying build/lib/django_mailman3/locale/crh/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/crh/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/co creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/co/LC_MESSAGES copying build/lib/django_mailman3/locale/co/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/co/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ckb creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ckb/LC_MESSAGES copying build/lib/django_mailman3/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ce creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ce/LC_MESSAGES copying build/lib/django_mailman3/locale/ce/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ce/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ca@valencia creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ca@valencia/LC_MESSAGES copying build/lib/django_mailman3/locale/ca@valencia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ca@valencia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ca creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ca/LC_MESSAGES copying build/lib/django_mailman3/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bs creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bs/LC_MESSAGES copying build/lib/django_mailman3/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/br creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/br/LC_MESSAGES copying build/lib/django_mailman3/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bo creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bo/LC_MESSAGES copying build/lib/django_mailman3/locale/bo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/bo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bn creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bn/LC_MESSAGES copying build/lib/django_mailman3/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bg creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bg/LC_MESSAGES copying build/lib/django_mailman3/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bem creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/bem/LC_MESSAGES copying build/lib/django_mailman3/locale/bem/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/bem/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/be creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/be/LC_MESSAGES copying build/lib/django_mailman3/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/az creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/az/LC_MESSAGES copying build/lib/django_mailman3/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ast creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ast/LC_MESSAGES copying build/lib/django_mailman3/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ar creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ar/LC_MESSAGES copying build/lib/django_mailman3/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/an creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/an/LC_MESSAGES copying build/lib/django_mailman3/locale/an/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/an/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/am creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/am/LC_MESSAGES copying build/lib/django_mailman3/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/am/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/af creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/af/LC_MESSAGES copying build/lib/django_mailman3/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_mailman3/lib creating build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth creating build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/provider.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/urls.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/views.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib/auth copying build/lib/django_mailman3/lib/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/mailman.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/paginator.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/scrub.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/user.py -> build/bdist.linux-x86_64/wheel/django_mailman3/lib creating build/bdist.linux-x86_64/wheel/django_mailman3/middleware copying build/lib/django_mailman3/middleware/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/middleware creating build/bdist.linux-x86_64/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/0002_maildomain.py -> build/bdist.linux-x86_64/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/migrations creating build/bdist.linux-x86_64/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/bootstrap_tags.py -> build/bdist.linux-x86_64/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/d_gravatar.py -> build/bdist.linux-x86_64/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/pagination.py -> build/bdist.linux-x86_64/wheel/django_mailman3/templatetags creating build/bdist.linux-x86_64/wheel/django_mailman3/tests creating build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/pipermail_nextpart.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/payload-utf8.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/payload-unknown.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/payload-iso8859.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/null_byte_multipart.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/null_byte.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/html-email-2.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/html-email-1.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/email-bad-filename.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/bad_charset.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-5.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-4.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-3.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-2.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-1.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attached_message.txt -> build/bdist.linux-x86_64/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/settings_test.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_bootstrap_tags.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_context_processors.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_forms.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_lib_auth_fedora_provider.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_lib_user.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_mailman.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_middlewares.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_paginator.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_scrub.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_signals.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_view_profile.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/urls_test.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/utils.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_delete_account.py -> build/bdist.linux-x86_64/wheel/django_mailman3/tests creating build/bdist.linux-x86_64/wheel/django_mailman3/views copying build/lib/django_mailman3/views/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3/views copying build/lib/django_mailman3/views/profile.py -> build/bdist.linux-x86_64/wheel/django_mailman3/views copying build/lib/django_mailman3/views/user_adapter.py -> build/bdist.linux-x86_64/wheel/django_mailman3/views copying build/lib/django_mailman3/__init__.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/admin.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/apps.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/context_processors.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/forms.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/models.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/signals.py -> build/bdist.linux-x86_64/wheel/django_mailman3 copying build/lib/django_mailman3/urls.py -> build/bdist.linux-x86_64/wheel/django_mailman3 running install_egg_info Copying django_mailman3.egg-info to build/bdist.linux-x86_64/wheel/django_mailman3-1.3.9-py3.12.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/django_mailman3-1.3.9.dist-info/WHEEL creating '/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir/pip-wheel-57wja506/.tmp-26bur7wi/django_mailman3-1.3.9-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'django_mailman3/__init__.py' adding 'django_mailman3/admin.py' adding 'django_mailman3/apps.py' adding 'django_mailman3/context_processors.py' adding 'django_mailman3/forms.py' adding 'django_mailman3/models.py' adding 'django_mailman3/signals.py' adding 'django_mailman3/urls.py' adding 'django_mailman3/lib/__init__.py' adding 'django_mailman3/lib/mailman.py' adding 'django_mailman3/lib/paginator.py' adding 'django_mailman3/lib/scrub.py' adding 'django_mailman3/lib/user.py' adding 'django_mailman3/lib/auth/__init__.py' adding 'django_mailman3/lib/auth/fedora/__init__.py' adding 'django_mailman3/lib/auth/fedora/provider.py' adding 'django_mailman3/lib/auth/fedora/urls.py' adding 'django_mailman3/lib/auth/fedora/views.py' adding 'django_mailman3/locale/af/LC_MESSAGES/django.po' adding 'django_mailman3/locale/am/LC_MESSAGES/django.po' adding 'django_mailman3/locale/an/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ar/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ast/LC_MESSAGES/django.po' adding 'django_mailman3/locale/az/LC_MESSAGES/django.po' adding 'django_mailman3/locale/be/LC_MESSAGES/django.po' adding 'django_mailman3/locale/bem/LC_MESSAGES/django.po' adding 'django_mailman3/locale/bg/LC_MESSAGES/django.po' adding 'django_mailman3/locale/bn/LC_MESSAGES/django.po' adding 'django_mailman3/locale/bo/LC_MESSAGES/django.po' adding 'django_mailman3/locale/br/LC_MESSAGES/django.po' adding 'django_mailman3/locale/bs/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ca/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ca@valencia/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ce/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ckb/LC_MESSAGES/django.po' adding 'django_mailman3/locale/co/LC_MESSAGES/django.po' adding 'django_mailman3/locale/crh/LC_MESSAGES/django.po' adding 'django_mailman3/locale/cs/LC_MESSAGES/django.po' adding 'django_mailman3/locale/cv/LC_MESSAGES/django.po' adding 'django_mailman3/locale/cy/LC_MESSAGES/django.po' adding 'django_mailman3/locale/da/LC_MESSAGES/django.po' adding 'django_mailman3/locale/de/LC_MESSAGES/django.po' adding 'django_mailman3/locale/el/LC_MESSAGES/django.po' adding 'django_mailman3/locale/en_AU/LC_MESSAGES/django.po' adding 'django_mailman3/locale/en_CA/LC_MESSAGES/django.po' adding 'django_mailman3/locale/en_GB/LC_MESSAGES/django.po' adding 'django_mailman3/locale/eo/LC_MESSAGES/django.po' adding 'django_mailman3/locale/es/LC_MESSAGES/django.po' adding 'django_mailman3/locale/et/LC_MESSAGES/django.po' adding 'django_mailman3/locale/eu/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fa/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fi/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fil/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fo/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fr/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fr_CA/LC_MESSAGES/django.po' adding 'django_mailman3/locale/frp/LC_MESSAGES/django.po' adding 'django_mailman3/locale/fy/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ga/LC_MESSAGES/django.po' adding 'django_mailman3/locale/gd/LC_MESSAGES/django.po' adding 'django_mailman3/locale/gl/LC_MESSAGES/django.po' adding 'django_mailman3/locale/gu/LC_MESSAGES/django.po' adding 'django_mailman3/locale/he/LC_MESSAGES/django.po' adding 'django_mailman3/locale/hi/LC_MESSAGES/django.po' adding 'django_mailman3/locale/hr/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ht/LC_MESSAGES/django.po' adding 'django_mailman3/locale/hu/LC_MESSAGES/django.po' adding 'django_mailman3/locale/hy/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ia/LC_MESSAGES/django.po' adding 'django_mailman3/locale/id/LC_MESSAGES/django.po' adding 'django_mailman3/locale/is/LC_MESSAGES/django.po' adding 'django_mailman3/locale/it/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ja/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ka/LC_MESSAGES/django.po' adding 'django_mailman3/locale/kk/LC_MESSAGES/django.po' adding 'django_mailman3/locale/kl/LC_MESSAGES/django.po' adding 'django_mailman3/locale/km/LC_MESSAGES/django.po' adding 'django_mailman3/locale/kn/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ko/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ku/LC_MESSAGES/django.po' adding 'django_mailman3/locale/kw/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ky/LC_MESSAGES/django.po' adding 'django_mailman3/locale/la/LC_MESSAGES/django.po' adding 'django_mailman3/locale/lb/LC_MESSAGES/django.po' adding 'django_mailman3/locale/lo/LC_MESSAGES/django.po' adding 'django_mailman3/locale/lt/LC_MESSAGES/django.po' adding 'django_mailman3/locale/lv/LC_MESSAGES/django.po' adding 'django_mailman3/locale/mg/LC_MESSAGES/django.po' adding 'django_mailman3/locale/mhr/LC_MESSAGES/django.po' adding 'django_mailman3/locale/mi/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ml/LC_MESSAGES/django.po' adding 'django_mailman3/locale/mr/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ms/LC_MESSAGES/django.po' adding 'django_mailman3/locale/my/LC_MESSAGES/django.po' adding 'django_mailman3/locale/nb_NO/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ne/LC_MESSAGES/django.po' adding 'django_mailman3/locale/nl/LC_MESSAGES/django.po' adding 'django_mailman3/locale/nn_NO/LC_MESSAGES/django.po' adding 'django_mailman3/locale/oc/LC_MESSAGES/django.po' adding 'django_mailman3/locale/os/LC_MESSAGES/django.po' adding 'django_mailman3/locale/pa/LC_MESSAGES/django.po' adding 'django_mailman3/locale/pl/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ps/LC_MESSAGES/django.po' adding 'django_mailman3/locale/pt/LC_MESSAGES/django.po' adding 'django_mailman3/locale/pt_BR/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ro/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ru/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sa/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sc/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sd/LC_MESSAGES/django.po' adding 'django_mailman3/locale/se/LC_MESSAGES/django.po' adding 'django_mailman3/locale/shn/LC_MESSAGES/django.po' adding 'django_mailman3/locale/si/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sk/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sl/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sq/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sr/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sv/LC_MESSAGES/django.po' adding 'django_mailman3/locale/sw/LC_MESSAGES/django.po' adding 'django_mailman3/locale/szl/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ta/LC_MESSAGES/django.po' adding 'django_mailman3/locale/te/LC_MESSAGES/django.po' adding 'django_mailman3/locale/tg/LC_MESSAGES/django.po' adding 'django_mailman3/locale/th/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ti/LC_MESSAGES/django.po' adding 'django_mailman3/locale/tr/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ug/LC_MESSAGES/django.po' adding 'django_mailman3/locale/uk/LC_MESSAGES/django.po' adding 'django_mailman3/locale/ur/LC_MESSAGES/django.po' adding 'django_mailman3/locale/uz/LC_MESSAGES/django.po' adding 'django_mailman3/locale/vi/LC_MESSAGES/django.po' adding 'django_mailman3/locale/wae/LC_MESSAGES/django.po' adding 'django_mailman3/locale/zh_CN/LC_MESSAGES/django.po' adding 'django_mailman3/locale/zh_HK/LC_MESSAGES/django.po' adding 'django_mailman3/locale/zh_TW/LC_MESSAGES/django.po' adding 'django_mailman3/middleware/__init__.py' adding 'django_mailman3/migrations/0001_initial.py' adding 'django_mailman3/migrations/0002_maildomain.py' adding 'django_mailman3/migrations/__init__.py' adding 'django_mailman3/static/django-mailman3/css/main.css' adding 'django_mailman3/static/django-mailman3/img/login/facebook.png' adding 'django_mailman3/static/django-mailman3/img/login/fedora.png' adding 'django_mailman3/static/django-mailman3/img/login/github.png' adding 'django_mailman3/static/django-mailman3/img/login/gitlab.png' adding 'django_mailman3/static/django-mailman3/img/login/google.png' adding 'django_mailman3/static/django-mailman3/img/login/openid.png' adding 'django_mailman3/static/django-mailman3/img/login/stackexchange.png' adding 'django_mailman3/static/django-mailman3/img/login/stackoverflow.png' adding 'django_mailman3/static/django-mailman3/img/login/twitter.png' adding 'django_mailman3/static/django-mailman3/img/login/yahoo.png' adding 'django_mailman3/static/django-mailman3/js/main.js' adding 'django_mailman3/templates/account/email.html' adding 'django_mailman3/templates/account/email_confirm.html' adding 'django_mailman3/templates/account/login.html' adding 'django_mailman3/templates/account/logout.html' adding 'django_mailman3/templates/account/password_change.html' adding 'django_mailman3/templates/account/password_reset.html' adding 'django_mailman3/templates/account/password_reset_from_key.html' adding 'django_mailman3/templates/account/password_set.html' adding 'django_mailman3/templates/account/signup.html' adding 'django_mailman3/templates/django_mailman3/base.html' adding 'django_mailman3/templates/django_mailman3/login_extra_post_providers.html' adding 'django_mailman3/templates/django_mailman3/login_extra_top.html' adding 'django_mailman3/templates/django_mailman3/bootstrap/form-horizontal.html' adding 'django_mailman3/templates/django_mailman3/bootstrap/form.html' adding 'django_mailman3/templates/django_mailman3/paginator/pagination.html' adding 'django_mailman3/templates/django_mailman3/profile/base.html' adding 'django_mailman3/templates/django_mailman3/profile/delete_profile.html' adding 'django_mailman3/templates/django_mailman3/profile/profile.html' adding 'django_mailman3/templates/openid/login.html' adding 'django_mailman3/templates/socialaccount/connections.html' adding 'django_mailman3/templates/socialaccount/signup.html' adding 'django_mailman3/templates/socialaccount/snippets/provider_list.html' adding 'django_mailman3/templatetags/__init__.py' adding 'django_mailman3/templatetags/bootstrap_tags.py' adding 'django_mailman3/templatetags/d_gravatar.py' adding 'django_mailman3/templatetags/pagination.py' adding 'django_mailman3/tests/__init__.py' adding 'django_mailman3/tests/settings_test.py' adding 'django_mailman3/tests/test_bootstrap_tags.py' adding 'django_mailman3/tests/test_context_processors.py' adding 'django_mailman3/tests/test_delete_account.py' adding 'django_mailman3/tests/test_forms.py' adding 'django_mailman3/tests/test_lib_auth_fedora_provider.py' adding 'django_mailman3/tests/test_lib_user.py' adding 'django_mailman3/tests/test_mailman.py' adding 'django_mailman3/tests/test_middlewares.py' adding 'django_mailman3/tests/test_paginator.py' adding 'django_mailman3/tests/test_scrub.py' adding 'django_mailman3/tests/test_signals.py' adding 'django_mailman3/tests/test_view_profile.py' adding 'django_mailman3/tests/urls_test.py' adding 'django_mailman3/tests/utils.py' adding 'django_mailman3/tests/testdata/attached_message.txt' adding 'django_mailman3/tests/testdata/attachment-1.txt' adding 'django_mailman3/tests/testdata/attachment-2.txt' adding 'django_mailman3/tests/testdata/attachment-3.txt' adding 'django_mailman3/tests/testdata/attachment-4.txt' adding 'django_mailman3/tests/testdata/attachment-5.txt' adding 'django_mailman3/tests/testdata/bad_charset.txt' adding 'django_mailman3/tests/testdata/email-bad-filename.txt' adding 'django_mailman3/tests/testdata/html-email-1.txt' adding 'django_mailman3/tests/testdata/html-email-2.txt' adding 'django_mailman3/tests/testdata/null_byte.txt' adding 'django_mailman3/tests/testdata/null_byte_multipart.txt' adding 'django_mailman3/tests/testdata/payload-iso8859.txt' adding 'django_mailman3/tests/testdata/payload-unknown.txt' adding 'django_mailman3/tests/testdata/payload-utf8.txt' adding 'django_mailman3/tests/testdata/pipermail_nextpart.txt' adding 'django_mailman3/views/__init__.py' adding 'django_mailman3/views/profile.py' adding 'django_mailman3/views/user_adapter.py' adding 'django_mailman3-1.3.9.dist-info/COPYING.txt' adding 'django_mailman3-1.3.9.dist-info/METADATA' adding 'django_mailman3-1.3.9.dist-info/WHEEL' adding 'django_mailman3-1.3.9.dist-info/top_level.txt' adding 'django_mailman3-1.3.9.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Building wheel for django-mailman3 (pyproject.toml): finished with status 'done' Created wheel for django-mailman3: filename=django_mailman3-1.3.9-py3-none-any.whl size=698596 sha256=98886d3ac8b6fa05a560af6a24b40fe04cb417a10967d5fc75fcab8d7877d57e Stored in directory: /builddir/.cache/pip/wheels/be/ba/0e/45a05a90e2fdc32ae1b81df3700462b7436076f2f7e290422a Successfully built django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.Y4qCpv + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 ++ dirname /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -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-mailman3-1.3.9 ++ ls /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir/django_mailman3-1.3.9-py3-none-any.whl ++ xargs basename --multiple ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=django_mailman3==1.3.9 + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir + /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 --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/django-mailman3-1.3.9/pyproject-wheeldir django_mailman3==1.3.9 Using pip 23.2.1 from /usr/lib/python3.12/site-packages/pip (python 3.12) Looking in links: /builddir/build/BUILD/django-mailman3-1.3.9/pyproject-wheeldir Processing ./pyproject-wheeldir/django_mailman3-1.3.9-py3-none-any.whl Installing collected packages: django_mailman3 Successfully installed django_mailman3-1.3.9 + '[' -d /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/bin ']' + rm -f /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-ghost-distinfo + site_dirs=() + '[' -d /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages ']' + site_dirs+=("/usr/lib/python3.12/site-packages") + '[' /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib64/python3.12/site-packages '!=' /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages ']' + '[' -d /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib64/python3.12/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info' + sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/redhat + /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 --record /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info/RECORD --output /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-record + rm -fv /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info/RECORD removed '/builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info/RECORD' + rm -fv /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info/REQUESTED removed '/builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12/site-packages/django_mailman3-1.3.9.dist-info/REQUESTED' ++ wc -l /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-ghost-distinfo ++ cut -f1 '-d ' + lines=1 + '[' 1 -ne 1 ']' + RPM_PERCENTAGES_COUNT=2 + /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-files --output-modules /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-modules --buildroot /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 --sitelib /usr/lib/python3.12/site-packages --sitearch /usr/lib64/python3.12/site-packages --python-version 3.12 --pyproject-record /builddir/build/BUILD/python-django-mailman3-1.3.9-1.fc40.x86_64-pyproject-record --prefix /usr django_mailman3 + /usr/bin/find-debuginfo -j4 --strict-build-id -m -i --build-id-seed 1.3.9-1.fc40 --unique-debug-suffix -1.3.9-1.fc40.x86_64 --unique-debug-src-base python-django-mailman3-1.3.9-1.fc40.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/django-mailman3-1.3.9 find-debuginfo: starting Extracting debug info from 0 files Creating .debug symlinks for symlinks to ELF files find: ‘debug’: No such file or directory find-debuginfo: done + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /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 + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j4 Bytecompiling .py files below /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/lib/python3.12 using python3.12 + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.6DgQZM + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -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-mailman3-1.3.9 + PYTHONPATH=.: + TOX_TESTENV_PASSENV='*' + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Werror=implicit-function-declaration -Werror=implicit-int -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 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + PATH=/builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin + PYTHONPATH=.: + PYTHONDONTWRITEBYTECODE=1 + PYTEST_ADDOPTS=' --ignore=/builddir/build/BUILD/django-mailman3-1.3.9/.pyproject-builddir' + PYTEST_XDIST_AUTO_NUM_WORKERS=4 + HOSTNAME=rpmbuild + /usr/bin/python3 -m tox --current-env -q --recreate -e py312 ============================= test session starts ============================== platform linux -- Python 3.12.0, pytest-7.4.3, pluggy-1.3.0 cachedir: .tox/py312/.pytest_cache django: settings: django_mailman3.tests.settings_test (from option) rootdir: /builddir/build/BUILD/django-mailman3-1.3.9 configfile: pytest.ini plugins: django-4.1.0 collected 82 items django_mailman3/tests/test_context_processors.py . django_mailman3/tests/test_delete_account.py .. django_mailman3/tests/test_forms.py ... django_mailman3/tests/test_lib_auth_fedora_provider.py .... django_mailman3/tests/test_lib_user.py .. django_mailman3/tests/test_mailman.py ................... django_mailman3/tests/test_middlewares.py ..... django_mailman3/tests/test_paginator.py .. django_mailman3/tests/test_signals.py ........... django_mailman3/tests/test_view_profile.py ... django_mailman3/tests/test_bootstrap_tags.py ...... django_mailman3/tests/test_paginator.py ....... django_mailman3/tests/test_scrub.py ................. =============================== warnings summary =============================== ../../../../usr/lib/python3.12/site-packages/django/conf/__init__.py:267 /usr/lib/python3.12/site-packages/django/conf/__init__.py:267: RemovedInDjango50Warning: The USE_L10N setting is deprecated. Starting with Django 5.0, localized formatting of data will always be enabled. For example Django will display numbers and dates using the format of the current locale. warnings.warn(USE_L10N_DEPRECATED_MSG, RemovedInDjango50Warning) ../../../../usr/lib/python3.12/site-packages/openid/oidutil.py:106 /usr/lib/python3.12/site-packages/openid/oidutil.py:106: DeprecationWarning: defusedxml.cElementTree is deprecated, import from defusedxml.ElementTree instead. ElementTree = __import__(mod_name, None, None, ['unused']) django_mailman3/tests/test_bootstrap_tags.py:29 /builddir/build/BUILD/django-mailman3-1.3.9/django_mailman3/tests/test_bootstrap_tags.py:29: PytestCollectionWarning: cannot collect test class 'TestForm' because it has a __init__ constructor (from: django_mailman3/tests/test_bootstrap_tags.py) class TestForm(Form): -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ======================== 82 passed, 3 warnings in 7.28s ======================== py312: OK (7.72 seconds) congratulations :) (7.76 seconds) + RPM_EC=0 ++ jobs -p + exit 0 Processing files: python3-django-mailman3-1.3.9-1.fc40.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.YKnxuN + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + DOCDIR=/builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/share/doc/python3-django-mailman3 + export LC_ALL= + LC_ALL= + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/share/doc/python3-django-mailman3 + cp -pr /builddir/build/BUILD/django-mailman3-1.3.9/README.rst /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/share/doc/python3-django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.wzLrDl + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + LICENSEDIR=/builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/share/licenses/python3-django-mailman3 + export LC_ALL= + LC_ALL= + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/share/licenses/python3-django-mailman3 + cp -pr /builddir/build/BUILD/django-mailman3-1.3.9/COPYING.txt /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64/usr/share/licenses/python3-django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-mailman3 = 1.3.9-1.fc40 python3-django-mailman3 = 1.3.9-1.fc40 python3.12-django-mailman3 = 1.3.9-1.fc40 python3.12dist(django-mailman3) = 1.3.9 python3dist(django-mailman3) = 1.3.9 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.12dist(django) < 4.3~~ with python3.12dist(django) >= 3.2) python(abi) = 3.12 python3.12dist(django-allauth) python3.12dist(django-gravatar2) >= 1.0.6 python3.12dist(mailmanclient) >= 3.3.3 python3.12dist(pytz) Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.9-1.fc40.src.rpm Wrote: /builddir/build/RPMS/python3-django-mailman3-1.3.9-1.fc40.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1ggKj6 + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.9 + /usr/bin/rm -rf /builddir/build/BUILDROOT/python-django-mailman3-1.3.9-1.fc40.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.0xwXG1 + umask 022 + cd /builddir/build/BUILD + rm -rf /builddir/build/BUILD/django-mailman3-1.3.9-SPECPARTS + rm -rf django-mailman3-1.3.9 django-mailman3-1.3.9.gemspec + RPM_EC=0 ++ jobs -p + exit 0 Finish: rpmbuild python-django-mailman3-1.3.9-1.fc40.src.rpm Finish: build phase for python-django-mailman3-1.3.9-1.fc40.src.rpm INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-rawhide-x86_64-1700753703.420278/root/var/log/dnf.rpm.log /var/lib/mock/fedora-rawhide-x86_64-1700753703.420278/root/var/log/dnf.librepo.log /var/lib/mock/fedora-rawhide-x86_64-1700753703.420278/root/var/log/dnf.log INFO: Done(/var/lib/copr-rpmbuild/results/python-django-mailman3-1.3.9-1.fc40.src.rpm) Config(child) 0 minutes 29 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-django-mailman3", "epoch": null, "version": "1.3.9", "release": "1.fc40", "arch": "src" }, { "name": "python3-django-mailman3", "epoch": null, "version": "1.3.9", "release": "1.fc40", "arch": "noarch" } ] } RPMResults finished