Warning: Permanently added '54.165.243.45' (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/7359057-fedora-rawhide-x86_64 --chroot fedora-rawhide-x86_64 Version: 0.72 PID: 6831 Logging PID: 6832 Task: {'allow_user_ssh': False, 'appstream': False, 'background': True, 'bootstrap': 'off', 'build_id': 7359057, 'buildroot_pkgs': [], 'chroot': 'fedora-rawhide-x86_64', 'enable_net': False, 'fedora_review': False, 'git_hash': 'fa5281c463146be5bde797d9d9f6663c8e4fbaed', 'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/@python/python3.13:pr:1/python-django-mailman3', 'isolation': 'default', 'memory_reqs': 2048, 'package_name': 'python-django-mailman3', 'package_version': '1.3.11-2', 'project_dirname': 'python3.13:pr:1', 'project_name': 'python3.13', 'project_owner': '@python', 'repo_priority': 9, 'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/@python/python3.13/fedora-rawhide-x86_64/', 'id': 'copr_base', 'name': 'Copr repository', 'priority': 9}, {'baseurl': 'http://kojipkgs.fedoraproject.org/repos/rawhide/latest/$basearch/', 'id': 'http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch', 'name': 'Additional repo http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch'}], 'sandbox': '@python/python3.13--https://src.fedoraproject.org/user/zlopez', 'source_json': {}, 'source_type': None, 'ssh_public_keys': None, 'submitter': 'https://src.fedoraproject.org/user/zlopez', 'tags': [], 'task_id': '7359057-fedora-rawhide-x86_64', 'timeout': 18000, 'uses_devel_repo': False, 'with_opts': [], 'without_opts': []} Running: git clone https://copr-dist-git.fedorainfracloud.org/git/@python/python3.13:pr:1/python-django-mailman3 /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3 --depth 500 --no-single-branch --recursive cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/@python/python3.13:pr:1/python-django-mailman3', '/var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3', '--depth', '500', '--no-single-branch', '--recursive'] cwd: . rc: 0 stdout: stderr: Cloning into '/var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3'... Running: git checkout fa5281c463146be5bde797d9d9f6663c8e4fbaed -- cmd: ['git', 'checkout', 'fa5281c463146be5bde797d9d9f6663c8e4fbaed', '--'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3 rc: 0 stdout: stderr: Note: switching to 'fa5281c463146be5bde797d9d9f6663c8e4fbaed'. 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 fa5281c automatic import of python-django-mailman3 Running: copr-distgit-client sources cmd: ['copr-distgit-client', 'sources'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/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.11.tar.gz INFO: Reading stdout from command: curl --help all INFO: Calling: curl -H Pragma: -o django-mailman3-1.3.11.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/@python/python3.13:pr:1/python-django-mailman3/django-mailman3-1.3.11.tar.gz/md5/3d1b596aeb0efe1eecdacf3b30ea51b2/django-mailman3-1.3.11.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed /usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated 100 408k 100 408k 0 0 24.2M 0 --:--:-- --:--:-- --:--:-- 24.9M INFO: Reading stdout from command: md5sum django-mailman3-1.3.11.tar.gz Running (timeout=18000): unbuffer mock --spec /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3/python-django-mailman3.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3 --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1714048811.076583 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 5.5 starting (python version = 3.12.1, NVR = mock-5.5-1.fc39), args: /usr/libexec/mock/mock --spec /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3/python-django-mailman3.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3 --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1714048811.076583 -r /var/lib/copr-rpmbuild/results/configs/child.cfg 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-a3xghms3/python-django-mailman3/python-django-mailman3.spec) Config(fedora-rawhide-x86_64) Start: clean chroot Finish: clean chroot Mock Version: 5.5 INFO: Mock Version: 5.5 Start: chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1714048811.076583/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin INFO: Package manager dnf5 detected and used (fallback) INFO: Buildroot is handled by package management from host and used with --installroot: rpm-4.19.1.1-1.fc39.x86_64 rpm-sequoia-1.6.0-1.fc39.x86_64 python3-dnf-4.19.2-1.fc39.noarch python3-dnf-plugins-core-4.6.0-1.fc39.noarch yum-4.19.2-1.fc39.noarch dnf5-5.1.17-1.fc39.x86_64 dnf5-plugins-5.1.17-1.fc39.x86_64 Start: installing minimal buildroot with dnf5 Updating and loading repositories: fedora 100% | 51.9 MiB/s | 41.0 MiB | 00m01s >>> Downloading successful, but checksum doesn't match. Calculated: 38ad29a8e245 >>> Status code: 404 for https://d2lzkl7pfhq30w.cloudfront.net/pub/fedora/linux/ Copr repository 100% | 46.6 MiB/s | 4.3 MiB | 00m00s Additional repo http_kojipkgs_fedorapr 100% | 44.8 MiB/s | 17.2 MiB | 00m00s Repositories loaded. Package Arch Version Repository Size Installing group/module packages: bash x86_64 5.2.26-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 8.1 MiB bzip2 x86_64 1.0.8-18.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 91.7 KiB coreutils x86_64 9.5-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 5.5 MiB cpio x86_64 2.15-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.1 MiB diffutils x86_64 3.10-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.6 MiB fedora-release-common noarch 41-0.9 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 19.2 KiB findutils x86_64 1:4.9.0-8.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.5 MiB gawk x86_64 5.3.0-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.7 MiB glibc-minimal-langpack x86_64 2.39.9000-14.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 0.0 B grep x86_64 3.11-7.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.0 MiB gzip x86_64 1.13-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 385.0 KiB info x86_64 7.1-2.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 357.8 KiB patch x86_64 2.7.6-24.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 262.8 KiB redhat-rpm-config noarch 288-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 183.3 KiB rpm-build x86_64 4.19.1.1-1.fc41 copr_base 173.7 KiB sed x86_64 4.9-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 861.5 KiB shadow-utils x86_64 2:4.15.1-2.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 4.1 MiB tar x86_64 2:1.35-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.9 MiB unzip x86_64 6.0-63.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 382.8 KiB util-linux x86_64 2.40-13.fc41 copr_base 3.7 MiB which x86_64 2.21-41.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 80.2 KiB xz x86_64 1:5.4.6-3.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.0 MiB Installing dependencies: alternatives x86_64 1.26-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 62.3 KiB ansible-srpm-macros noarch 1-15.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 35.7 KiB audit-libs x86_64 4.0.1-1.fc41 copr_base 327.3 KiB authselect x86_64 1.5.0-5.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 153.6 KiB authselect-libs x86_64 1.5.0-5.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 818.2 KiB basesystem noarch 11-20.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 0.0 B binutils x86_64 2.42.50-6.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 27.2 MiB binutils-gold x86_64 2.42.50-6.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.0 MiB bzip2-libs x86_64 1.0.8-18.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 80.7 KiB ca-certificates noarch 2023.2.62_v7.0.401-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.3 MiB coreutils-common x86_64 9.5-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 11.2 MiB cracklib x86_64 2.9.11-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 238.9 KiB crypto-policies noarch 20240320-1.git58e3d95.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 119.2 KiB curl x86_64 8.7.1-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 758.1 KiB cyrus-sasl-lib x86_64 2.1.28-19.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.3 MiB debugedit x86_64 5.0-14.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 199.0 KiB dwz x86_64 0.15-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 290.9 KiB ed x86_64 1.20.2-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 146.8 KiB efi-srpm-macros noarch 5-11.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 40.1 KiB elfutils x86_64 0.191-7.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.5 MiB elfutils-debuginfod-client x86_64 0.191-7.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 64.9 KiB elfutils-default-yama-scope noarch 0.191-7.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.8 KiB elfutils-libelf x86_64 0.191-7.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.2 MiB elfutils-libs x86_64 0.191-7.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 646.1 KiB fedora-gpg-keys noarch 41-0.1 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 125.0 KiB fedora-release noarch 41-0.9 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 0.0 B fedora-release-identity-basic noarch 41-0.9 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 694.0 B fedora-repos noarch 41-0.1 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 4.9 KiB fedora-repos-rawhide noarch 41-0.1 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.2 KiB file x86_64 5.45-5.fc41 copr_base 103.5 KiB file-libs x86_64 5.45-5.fc41 copr_base 9.9 MiB filesystem x86_64 3.18-9.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 106.0 B fonts-srpm-macros noarch 1:2.0.5-14.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 55.3 KiB forge-srpm-macros noarch 0.3.1-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 39.0 KiB fpc-srpm-macros noarch 1.3-12.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 144.0 B gdb-minimal x86_64 14.2-5.fc41 copr_base 12.7 MiB gdbm x86_64 1:1.23-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 460.9 KiB gdbm-libs x86_64 1:1.23-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 121.9 KiB ghc-srpm-macros noarch 1.9.1-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 747.0 B glibc x86_64 2.39.9000-14.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 6.7 MiB glibc-common x86_64 2.39.9000-14.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.0 MiB glibc-gconv-extra x86_64 2.39.9000-14.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 7.8 MiB gmp x86_64 1:6.3.0-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 803.4 KiB gnat-srpm-macros noarch 6-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.0 KiB go-srpm-macros noarch 3.6.0-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 60.8 KiB jansson x86_64 2.13.1-9.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 88.3 KiB kernel-srpm-macros noarch 1.0-23.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.9 KiB keyutils-libs x86_64 1.6.3-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 54.4 KiB krb5-libs x86_64 1.21.2-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.3 MiB libacl x86_64 2.3.2-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 40.0 KiB libarchive x86_64 3.7.2-3.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 914.6 KiB libattr x86_64 2.5.2-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 28.5 KiB libblkid x86_64 2.40-13.fc41 copr_base 262.5 KiB libbrotli x86_64 1.1.0-3.fc41 copr_base 829.6 KiB libcap x86_64 2.69-8.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 219.7 KiB libcap-ng x86_64 0.8.5-1.fc41 copr_base 69.1 KiB libcom_err x86_64 1.47.0-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 67.2 KiB libcurl x86_64 8.7.1-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 793.5 KiB libeconf x86_64 0.6.2-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 58.0 KiB libevent x86_64 2.1.12-12.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 895.6 KiB libfdisk x86_64 2.40-13.fc41 copr_base 362.9 KiB libffi x86_64 3.4.6-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 82.4 KiB libgcc x86_64 14.0.1-0.15.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 270.6 KiB libgomp x86_64 14.0.1-0.15.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 519.2 KiB libidn2 x86_64 2.3.7-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 329.1 KiB libmount x86_64 2.40-13.fc41 copr_base 351.8 KiB libnghttp2 x86_64 1.61.0-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 166.1 KiB libnsl2 x86_64 2.0.1-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 57.9 KiB libpkgconf x86_64 2.1.0-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 74.2 KiB libpsl x86_64 0.21.5-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 80.5 KiB libpwquality x86_64 1.4.5-9.fc41 copr_base 417.8 KiB libselinux x86_64 3.6-5.fc41 copr_base 177.0 KiB libsemanage x86_64 3.6-3.fc41 copr_base 293.5 KiB libsepol x86_64 3.6-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 802.0 KiB libsmartcols x86_64 2.40-13.fc41 copr_base 180.4 KiB libssh x86_64 0.10.6-6.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 513.3 KiB libssh-config noarch 0.10.6-6.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 277.0 B libstdc++ x86_64 14.0.1-0.15.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.8 MiB libtasn1 x86_64 4.19.0-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 175.7 KiB libtirpc x86_64 1.3.4-1.rc3.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 202.8 KiB libtool-ltdl x86_64 2.4.7-10.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 66.2 KiB libunistring x86_64 1.1-7.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.7 MiB libutempter x86_64 1.2.1-13.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 57.7 KiB libuuid x86_64 2.40-13.fc41 copr_base 37.4 KiB libverto x86_64 0.3.2-8.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 29.5 KiB libxcrypt x86_64 4.4.36-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 262.8 KiB libxml2 x86_64 2.12.6-1.fc41 copr_base 1.7 MiB libzstd x86_64 1.5.6-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 787.9 KiB lua-libs x86_64 5.4.6-5.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 281.1 KiB lua-srpm-macros noarch 1-13.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.3 KiB lz4-libs x86_64 1.9.4-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 129.4 KiB mpfr x86_64 4.2.1-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 832.0 KiB ncurses-base noarch 6.4-12.20240127.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 326.2 KiB ncurses-libs x86_64 6.4-12.20240127.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 963.2 KiB ocaml-srpm-macros noarch 9-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.9 KiB openblas-srpm-macros noarch 2-17.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 112.0 B openldap x86_64 2.6.7-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 635.1 KiB openssl-libs x86_64 1:3.2.1-6.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 7.8 MiB p11-kit x86_64 0.25.3-4.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.2 MiB p11-kit-trust x86_64 0.25.3-4.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 391.4 KiB package-notes-srpm-macros noarch 0.5-11.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.6 KiB pam x86_64 1.6.1-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.8 MiB pam-libs x86_64 1.6.1-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 135.0 KiB pcre2 x86_64 10.43-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 653.5 KiB pcre2-syntax noarch 10.43-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 249.0 KiB perl-srpm-macros noarch 1-53.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 861.0 B pkgconf x86_64 2.1.0-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 82.4 KiB pkgconf-m4 noarch 2.1.0-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 13.9 KiB pkgconf-pkg-config x86_64 2.1.0-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 989.0 B popt x86_64 1.19-6.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 136.9 KiB publicsuffix-list-dafsa noarch 20240107-3.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 67.5 KiB pyproject-srpm-macros noarch 1.12.0-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.5 KiB python-srpm-macros noarch 3.13-5.fc40 copr_base 50.1 KiB qt5-srpm-macros noarch 5.15.13-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 492.0 B qt6-srpm-macros noarch 6.7.0-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 456.0 B readline x86_64 8.2-8.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 489.2 KiB rpm x86_64 4.19.1.1-1.fc41 copr_base 3.0 MiB rpm-build-libs x86_64 4.19.1.1-1.fc41 copr_base 198.4 KiB rpm-libs x86_64 4.19.1.1-1.fc41 copr_base 709.9 KiB rpm-sequoia x86_64 1.6.0-2.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 2.2 MiB rust-srpm-macros noarch 26.2-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 4.8 KiB setup noarch 2.14.5-2.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 720.4 KiB sqlite-libs x86_64 3.45.2-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.4 MiB systemd-libs x86_64 255.5-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.9 MiB util-linux-core x86_64 2.40-13.fc41 copr_base 1.5 MiB xxhash-libs x86_64 0.8.2-2.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 88.5 KiB xz-libs x86_64 1:5.4.6-3.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 209.8 KiB zig-srpm-macros noarch 1-2.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.1 KiB zip x86_64 3.0-40.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 703.2 KiB zlib-ng-compat x86_64 2.1.6-2.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 134.0 KiB zstd x86_64 1.5.6-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.7 MiB Installing groups: Buildsystem building group Transaction Summary: Installing: 153 packages Total size of inbound packages is 52 MiB. Need to download 52 MiB. After this operation 179 MiB will be used (install 179 MiB, remove 0 B). [ 1/153] bzip2-0:1.0.8-18.fc40.x86_64 100% | 557.0 KiB/s | 52.4 KiB | 00m00s [ 2/153] bash-0:5.2.26-3.fc40.x86_64 100% | 16.1 MiB/s | 1.8 MiB | 00m00s [ 3/153] diffutils-0:3.10-5.fc40.x86_6 100% | 18.5 MiB/s | 396.8 KiB | 00m00s [ 4/153] fedora-release-common-0:41-0. 100% | 1.1 MiB/s | 21.5 KiB | 00m00s [ 5/153] cpio-0:2.15-1.fc40.x86_64 100% | 4.4 MiB/s | 285.1 KiB | 00m00s [ 6/153] coreutils-0:9.5-1.fc41.x86_64 100% | 6.7 MiB/s | 1.1 MiB | 00m00s [ 7/153] glibc-minimal-langpack-0:2.39 100% | 4.9 MiB/s | 109.5 KiB | 00m00s [ 8/153] findutils-1:4.9.0-8.fc40.x86_ 100% | 12.4 MiB/s | 482.5 KiB | 00m00s [ 9/153] gawk-0:5.3.0-3.fc40.x86_64 100% | 27.9 MiB/s | 1.1 MiB | 00m00s [ 10/153] grep-0:3.11-7.fc40.x86_64 100% | 10.5 MiB/s | 289.7 KiB | 00m00s [ 11/153] gzip-0:1.13-1.fc40.x86_64 100% | 6.4 MiB/s | 164.0 KiB | 00m00s [ 12/153] info-0:7.1-2.fc40.x86_64 100% | 8.5 MiB/s | 182.3 KiB | 00m00s [ 13/153] rpm-build-0:4.19.1.1-1.fc41.x 100% | 8.6 MiB/s | 70.8 KiB | 00m00s [ 14/153] patch-0:2.7.6-24.fc40.x86_64 100% | 4.9 MiB/s | 130.7 KiB | 00m00s [ 15/153] redhat-rpm-config-0:288-1.fc4 100% | 3.1 MiB/s | 75.3 KiB | 00m00s [ 16/153] sed-0:4.9-1.fc40.x86_64 100% | 14.4 MiB/s | 309.2 KiB | 00m00s [ 17/153] unzip-0:6.0-63.fc40.x86_64 100% | 9.5 MiB/s | 184.5 KiB | 00m00s [ 18/153] util-linux-0:2.40-13.fc41.x86 100% | 192.6 MiB/s | 1.2 MiB | 00m00s [ 19/153] shadow-utils-2:4.15.1-2.fc41. 100% | 32.4 MiB/s | 1.3 MiB | 00m00s [ 20/153] tar-2:1.35-3.fc40.x86_64 100% | 19.2 MiB/s | 847.4 KiB | 00m00s [ 21/153] rpm-0:4.19.1.1-1.fc41.x86_64 100% | 166.2 MiB/s | 510.5 KiB | 00m00s [ 22/153] rpm-libs-0:4.19.1.1-1.fc41.x8 100% | 150.8 MiB/s | 308.8 KiB | 00m00s [ 23/153] rpm-build-libs-0:4.19.1.1-1.f 100% | 46.6 MiB/s | 95.4 KiB | 00m00s [ 24/153] xz-1:5.4.6-3.fc41.x86_64 100% | 17.3 MiB/s | 531.9 KiB | 00m00s [ 25/153] which-0:2.21-41.fc40.x86_64 100% | 1.1 MiB/s | 41.4 KiB | 00m00s [ 26/153] bzip2-libs-0:1.0.8-18.fc40.x8 100% | 1.5 MiB/s | 40.9 KiB | 00m00s [ 27/153] xz-libs-1:5.4.6-3.fc41.x86_64 100% | 2.8 MiB/s | 110.2 KiB | 00m00s [ 28/153] glibc-0:2.39.9000-14.fc41.x86 100% | 40.0 MiB/s | 2.2 MiB | 00m00s [ 29/153] libselinux-0:3.6-5.fc41.x86_6 100% | 42.8 MiB/s | 87.7 KiB | 00m00s [ 30/153] audit-libs-0:4.0.1-1.fc41.x86 100% | 61.4 MiB/s | 125.8 KiB | 00m00s [ 31/153] libacl-0:2.3.2-1.fc40.x86_64 100% | 872.5 KiB/s | 24.4 KiB | 00m00s [ 32/153] libsemanage-0:3.6-3.fc41.x86_ 100% | 22.8 MiB/s | 116.8 KiB | 00m00s [ 33/153] libeconf-0:0.6.2-1.fc41.x86_6 100% | 1.2 MiB/s | 31.9 KiB | 00m00s [ 34/153] libattr-0:2.5.2-3.fc40.x86_64 100% | 473.6 KiB/s | 18.0 KiB | 00m00s [ 35/153] libxcrypt-0:4.4.36-5.fc40.x86 100% | 3.8 MiB/s | 118.1 KiB | 00m00s [ 36/153] pam-libs-0:1.6.1-1.fc41.x86_6 100% | 1.7 MiB/s | 56.9 KiB | 00m00s [ 37/153] setup-0:2.14.5-2.fc40.noarch 100% | 5.0 MiB/s | 148.1 KiB | 00m00s [ 38/153] ansible-srpm-macros-0:1-15.fc 100% | 673.2 KiB/s | 20.9 KiB | 00m00s [ 39/153] glibc-gconv-extra-0:2.39.9000 100% | 31.4 MiB/s | 1.6 MiB | 00m00s [ 40/153] dwz-0:0.15-6.fc40.x86_64 100% | 3.8 MiB/s | 137.8 KiB | 00m00s [ 41/153] file-0:5.45-5.fc41.x86_64 100% | 24.2 MiB/s | 49.6 KiB | 00m00s [ 42/153] efi-srpm-macros-0:5-11.fc40.n 100% | 825.9 KiB/s | 22.3 KiB | 00m00s [ 43/153] forge-srpm-macros-0:0.3.1-1.f 100% | 843.6 KiB/s | 19.4 KiB | 00m00s [ 44/153] fonts-srpm-macros-1:2.0.5-14. 100% | 1.0 MiB/s | 26.5 KiB | 00m00s [ 45/153] fpc-srpm-macros-0:1.3-12.fc40 100% | 252.7 KiB/s | 7.8 KiB | 00m00s [ 46/153] ghc-srpm-macros-0:1.9.1-1.fc4 100% | 309.3 KiB/s | 9.0 KiB | 00m00s [ 47/153] gnat-srpm-macros-0:6-5.fc40.n 100% | 232.2 KiB/s | 8.8 KiB | 00m00s [ 48/153] go-srpm-macros-0:3.6.0-1.fc41 100% | 994.9 KiB/s | 27.9 KiB | 00m00s [ 49/153] kernel-srpm-macros-0:1.0-23.f 100% | 375.5 KiB/s | 9.8 KiB | 00m00s [ 50/153] lua-srpm-macros-0:1-13.fc40.n 100% | 281.6 KiB/s | 8.7 KiB | 00m00s [ 51/153] ocaml-srpm-macros-0:9-3.fc40. 100% | 312.9 KiB/s | 9.1 KiB | 00m00s [ 52/153] openblas-srpm-macros-0:2-17.f 100% | 306.4 KiB/s | 7.7 KiB | 00m00s [ 53/153] package-notes-srpm-macros-0:0 100% | 331.5 KiB/s | 9.9 KiB | 00m00s [ 54/153] python-srpm-macros-0:3.13-5.f 100% | 8.3 MiB/s | 25.3 KiB | 00m00s [ 55/153] pyproject-srpm-macros-0:1.12. 100% | 504.8 KiB/s | 13.6 KiB | 00m00s [ 56/153] perl-srpm-macros-0:1-53.fc40. 100% | 204.4 KiB/s | 8.4 KiB | 00m00s [ 57/153] qt5-srpm-macros-0:5.15.13-1.f 100% | 256.9 KiB/s | 8.5 KiB | 00m00s [ 58/153] qt6-srpm-macros-0:6.7.0-1.fc4 100% | 289.4 KiB/s | 9.0 KiB | 00m00s [ 59/153] rust-srpm-macros-0:26.2-1.fc4 100% | 502.5 KiB/s | 12.6 KiB | 00m00s [ 60/153] zig-srpm-macros-0:1-2.fc40.no 100% | 268.0 KiB/s | 8.0 KiB | 00m00s [ 61/153] zip-0:3.0-40.fc40.x86_64 100% | 7.2 MiB/s | 264.8 KiB | 00m00s [ 62/153] ed-0:1.20.2-1.fc41.x86_64 100% | 2.7 MiB/s | 81.9 KiB | 00m00s [ 63/153] ncurses-libs-0:6.4-12.2024012 100% | 10.1 MiB/s | 332.5 KiB | 00m00s [ 64/153] glibc-common-0:2.39.9000-14.f 100% | 12.8 MiB/s | 392.1 KiB | 00m00s [ 65/153] pcre2-0:10.43-1.fc41.x86_64 100% | 6.9 MiB/s | 241.9 KiB | 00m00s [ 66/153] basesystem-0:11-20.fc40.noarc 100% | 287.5 KiB/s | 7.2 KiB | 00m00s [ 67/153] libgcc-0:14.0.1-0.15.fc41.x86 100% | 4.5 MiB/s | 125.6 KiB | 00m00s [ 68/153] filesystem-0:3.18-9.fc41.x86_ 100% | 28.1 MiB/s | 1.1 MiB | 00m00s [ 69/153] gmp-1:6.3.0-1.fc41.x86_64 100% | 10.7 MiB/s | 316.8 KiB | 00m00s [ 70/153] mpfr-0:4.2.1-3.fc40.x86_64 100% | 6.6 MiB/s | 349.0 KiB | 00m00s [ 71/153] fedora-repos-0:41-0.1.noarch 100% | 267.0 KiB/s | 9.3 KiB | 00m00s [ 72/153] readline-0:8.2-8.fc40.x86_64 100% | 3.5 MiB/s | 213.3 KiB | 00m00s [ 73/153] elfutils-libelf-0:0.191-7.fc4 100% | 7.3 MiB/s | 208.5 KiB | 00m00s [ 74/153] coreutils-common-0:9.5-1.fc41 100% | 51.1 MiB/s | 2.1 MiB | 00m00s [ 75/153] libcap-0:2.69-8.fc41.x86_64 100% | 2.6 MiB/s | 85.5 KiB | 00m00s [ 76/153] libblkid-0:2.40-13.fc41.x86_6 100% | 60.9 MiB/s | 124.8 KiB | 00m00s [ 77/153] libcap-ng-0:0.8.5-1.fc41.x86_ 100% | 16.0 MiB/s | 32.8 KiB | 00m00s [ 78/153] libfdisk-0:2.40-13.fc41.x86_6 100% | 78.0 MiB/s | 159.7 KiB | 00m00s [ 79/153] libmount-0:2.40-13.fc41.x86_6 100% | 75.8 MiB/s | 155.2 KiB | 00m00s [ 80/153] libsmartcols-0:2.40-13.fc41.x 100% | 81.8 MiB/s | 83.8 KiB | 00m00s [ 81/153] authselect-libs-0:1.5.0-5.fc4 100% | 7.7 MiB/s | 204.9 KiB | 00m00s [ 82/153] libuuid-0:2.40-13.fc41.x86_64 100% | 14.1 MiB/s | 28.9 KiB | 00m00s [ 83/153] openssl-libs-1:3.2.1-6.fc41.x 100% | 41.9 MiB/s | 2.3 MiB | 00m00s [ 84/153] libutempter-0:1.2.1-13.fc40.x 100% | 628.7 KiB/s | 26.4 KiB | 00m00s [ 85/153] util-linux-core-0:2.40-13.fc4 100% | 101.6 MiB/s | 520.3 KiB | 00m00s [ 86/153] pam-0:1.6.1-1.fc41.x86_64 100% | 11.0 MiB/s | 516.8 KiB | 00m00s [ 87/153] systemd-libs-0:255.5-1.fc41.x 100% | 13.8 MiB/s | 706.1 KiB | 00m00s [ 88/153] zlib-ng-compat-0:2.1.6-2.fc40 100% | 3.0 MiB/s | 77.1 KiB | 00m00s [ 89/153] libzstd-0:1.5.6-1.fc41.x86_64 100% | 9.1 MiB/s | 308.9 KiB | 00m00s [ 90/153] lua-libs-0:5.4.6-5.fc40.x86_6 100% | 3.8 MiB/s | 131.9 KiB | 00m00s [ 91/153] popt-0:1.19-6.fc40.x86_64 100% | 1.4 MiB/s | 59.6 KiB | 00m00s [ 92/153] rpm-sequoia-0:1.6.0-2.fc40.x8 100% | 16.6 MiB/s | 847.5 KiB | 00m00s [ 93/153] file-libs-0:5.45-5.fc41.x86_6 100% | 93.1 MiB/s | 762.3 KiB | 00m00s [ 94/153] elfutils-libs-0:0.191-7.fc41. 100% | 7.0 MiB/s | 258.1 KiB | 00m00s [ 95/153] sqlite-libs-0:3.45.2-1.fc41.x 100% | 12.5 MiB/s | 705.7 KiB | 00m00s [ 96/153] debugedit-0:5.0-14.fc40.x86_6 100% | 3.7 MiB/s | 78.7 KiB | 00m00s [ 97/153] libgomp-0:14.0.1-0.15.fc41.x8 100% | 7.0 MiB/s | 345.7 KiB | 00m00s [ 98/153] elfutils-0:0.191-7.fc41.x86_6 100% | 16.0 MiB/s | 524.4 KiB | 00m00s [ 99/153] pkgconf-pkg-config-0:2.1.0-1. 100% | 285.4 KiB/s | 9.7 KiB | 00m00s [100/153] zstd-0:1.5.6-1.fc41.x86_64 100% | 17.3 MiB/s | 479.3 KiB | 00m00s [101/153] binutils-0:2.42.50-6.fc41.x86 100% | 58.5 MiB/s | 6.3 MiB | 00m00s [102/153] curl-0:8.7.1-1.fc41.x86_64 100% | 9.6 MiB/s | 305.9 KiB | 00m00s [103/153] libarchive-0:3.7.2-3.fc41.x86 100% | 14.7 MiB/s | 406.6 KiB | 00m00s [104/153] libsepol-0:3.6-3.fc40.x86_64 100% | 7.5 MiB/s | 340.1 KiB | 00m00s [105/153] lz4-libs-0:1.9.4-6.fc40.x86_6 100% | 1.5 MiB/s | 67.2 KiB | 00m00s [106/153] libstdc++-0:14.0.1-0.15.fc41. 100% | 15.9 MiB/s | 880.7 KiB | 00m00s [107/153] pkgconf-m4-0:2.1.0-1.fc40.noa 100% | 480.1 KiB/s | 13.9 KiB | 00m00s [108/153] pkgconf-0:2.1.0-1.fc40.x86_64 100% | 925.4 KiB/s | 43.5 KiB | 00m00s [109/153] libpkgconf-0:2.1.0-1.fc40.x86 100% | 995.5 KiB/s | 37.8 KiB | 00m00s [110/153] pcre2-syntax-0:10.43-1.fc41.n 100% | 4.4 MiB/s | 148.8 KiB | 00m00s [111/153] gdbm-1:1.23-6.fc40.x86_64 100% | 5.3 MiB/s | 147.4 KiB | 00m00s [112/153] authselect-0:1.5.0-5.fc41.x86 100% | 4.3 MiB/s | 141.1 KiB | 00m00s [113/153] libpwquality-0:1.4.5-9.fc41.x 100% | 35.4 MiB/s | 108.8 KiB | 00m00s [114/153] gdbm-libs-1:1.23-6.fc40.x86_6 100% | 1.8 MiB/s | 56.2 KiB | 00m00s [115/153] libnsl2-0:2.0.1-1.fc40.x86_64 100% | 924.0 KiB/s | 29.6 KiB | 00m00s [116/153] libtirpc-0:1.3.4-1.rc3.fc41.x 100% | 3.1 MiB/s | 92.5 KiB | 00m00s [117/153] crypto-policies-0:20240320-1. 100% | 2.5 MiB/s | 64.9 KiB | 00m00s [118/153] ncurses-base-0:6.4-12.2024012 100% | 2.8 MiB/s | 63.8 KiB | 00m00s [119/153] ca-certificates-0:2023.2.62_v 100% | 18.7 MiB/s | 862.1 KiB | 00m00s [120/153] libxml2-0:2.12.6-1.fc41.x86_6 100% | 167.4 MiB/s | 685.6 KiB | 00m00s [121/153] libcom_err-0:1.47.0-5.fc40.x8 100% | 845.1 KiB/s | 25.4 KiB | 00m00s [122/153] keyutils-libs-0:1.6.3-3.fc40. 100% | 1.5 MiB/s | 31.5 KiB | 00m00s [123/153] fedora-gpg-keys-0:41-0.1.noar 100% | 5.6 MiB/s | 121.0 KiB | 00m00s [124/153] krb5-libs-0:1.21.2-5.fc40.x86 100% | 11.5 MiB/s | 751.4 KiB | 00m00s [125/153] libverto-0:0.3.2-8.fc40.x86_6 100% | 540.5 KiB/s | 20.5 KiB | 00m00s [126/153] fedora-repos-rawhide-0:41-0.1 100% | 241.1 KiB/s | 8.9 KiB | 00m00s [127/153] elfutils-debuginfod-client-0: 100% | 1.2 MiB/s | 38.2 KiB | 00m00s [128/153] elfutils-default-yama-scope-0 100% | 333.7 KiB/s | 13.3 KiB | 00m00s [129/153] alternatives-0:1.26-3.fc40.x8 100% | 1.4 MiB/s | 39.9 KiB | 00m00s [130/153] p11-kit-trust-0:0.25.3-4.fc40 100% | 4.0 MiB/s | 131.5 KiB | 00m00s [131/153] p11-kit-0:0.25.3-4.fc40.x86_6 100% | 11.9 MiB/s | 475.5 KiB | 00m00s [132/153] jansson-0:2.13.1-9.fc40.x86_6 100% | 1.3 MiB/s | 44.2 KiB | 00m00s [133/153] cracklib-0:2.9.11-5.fc40.x86_ 100% | 2.2 MiB/s | 81.6 KiB | 00m00s [134/153] binutils-gold-0:2.42.50-6.fc4 100% | 17.0 MiB/s | 783.2 KiB | 00m00s [135/153] libtasn1-0:4.19.0-6.fc40.x86_ 100% | 2.6 MiB/s | 73.7 KiB | 00m00s [136/153] libffi-0:3.4.6-1.fc41.x86_64 100% | 1.3 MiB/s | 40.0 KiB | 00m00s [137/153] fedora-release-0:41-0.9.noarc 100% | 440.4 KiB/s | 11.0 KiB | 00m00s [138/153] gdb-minimal-0:14.2-5.fc41.x86 100% | 252.0 MiB/s | 4.3 MiB | 00m00s [139/153] fedora-release-identity-basic 100% | 437.1 KiB/s | 11.8 KiB | 00m00s [140/153] libbrotli-0:1.1.0-3.fc41.x86_ 100% | 110.1 MiB/s | 338.2 KiB | 00m00s [141/153] libcurl-0:8.7.1-1.fc41.x86_64 100% | 8.0 MiB/s | 352.2 KiB | 00m00s [142/153] xxhash-libs-0:0.8.2-2.fc40.x8 100% | 947.2 KiB/s | 36.9 KiB | 00m00s [143/153] libidn2-0:2.3.7-1.fc40.x86_64 100% | 3.1 MiB/s | 112.4 KiB | 00m00s [144/153] libnghttp2-0:1.61.0-1.fc41.x8 100% | 2.3 MiB/s | 76.3 KiB | 00m00s [145/153] libssh-0:0.10.6-6.fc41.x86_64 100% | 5.4 MiB/s | 211.5 KiB | 00m00s [146/153] libpsl-0:0.21.5-3.fc40.x86_64 100% | 1.5 MiB/s | 63.9 KiB | 00m00s [147/153] openldap-0:2.6.7-1.fc40.x86_6 100% | 9.2 MiB/s | 254.3 KiB | 00m00s [148/153] libevent-0:2.1.12-12.fc40.x86 100% | 7.2 MiB/s | 257.2 KiB | 00m00s [149/153] cyrus-sasl-lib-0:2.1.28-19.fc 100% | 15.7 MiB/s | 789.3 KiB | 00m00s [150/153] libtool-ltdl-0:2.4.7-10.fc40. 100% | 737.9 KiB/s | 36.2 KiB | 00m00s [151/153] libunistring-0:1.1-7.fc41.x86 100% | 15.2 MiB/s | 545.4 KiB | 00m00s [152/153] libssh-config-0:0.10.6-6.fc41 100% | 166.1 KiB/s | 9.1 KiB | 00m00s [153/153] publicsuffix-list-dafsa-0:202 100% | 829.8 KiB/s | 58.1 KiB | 00m00s -------------------------------------------------------------------------------- [153/153] Total 100% | 30.6 MiB/s | 52.2 MiB | 00m02s Running transaction [ 1/155] Verify package files 100% | 864.0 B/s | 153.0 B | 00m00s >>> Running pre-transaction scriptlet: filesystem-0:3.18-9.fc41.x86_64 >>> Stop pre-transaction scriptlet: filesystem-0:3.18-9.fc41.x86_64 [ 2/155] Prepare transaction 100% | 4.2 KiB/s | 153.0 B | 00m00s [ 3/155] Installing libgcc-0:14.0.1-0. 100% | 265.8 MiB/s | 272.2 KiB | 00m00s >>> Running post-install scriptlet: libgcc-0:14.0.1-0.15.fc41.x86_64 >>> Stop post-install scriptlet: libgcc-0:14.0.1-0.15.fc41.x86_64 [ 4/155] Installing crypto-policies-0: 100% | 35.7 MiB/s | 146.2 KiB | 00m00s >>> Running post-install scriptlet: crypto-policies-0:20240320-1.git58e3d95.fc41 >>> Stop post-install scriptlet: crypto-policies-0:20240320-1.git58e3d95.fc41.no [ 5/155] Installing fedora-release-ide 100% | 0.0 B/s | 952.0 B | 00m00s [ 6/155] Installing fedora-gpg-keys-0: 100% | 55.4 MiB/s | 170.1 KiB | 00m00s [ 7/155] Installing fedora-repos-rawhi 100% | 0.0 B/s | 2.4 KiB | 00m00s [ 8/155] Installing fedora-repos-0:41- 100% | 0.0 B/s | 5.7 KiB | 00m00s [ 9/155] Installing fedora-release-com 100% | 22.7 MiB/s | 23.3 KiB | 00m00s [ 10/155] Installing fedora-release-0:4 100% | 0.0 B/s | 124.0 B | 00m00s [ 11/155] Installing setup-0:2.14.5-2.f 100% | 64.4 MiB/s | 725.8 KiB | 00m00s >>> Running post-install scriptlet: setup-0:2.14.5-2.fc40.noarch >>> Stop post-install scriptlet: setup-0:2.14.5-2.fc40.noarch [ 12/155] Installing filesystem-0:3.18- 100% | 3.3 MiB/s | 212.5 KiB | 00m00s [ 13/155] Installing basesystem-0:11-20 100% | 0.0 B/s | 124.0 B | 00m00s [ 14/155] Installing publicsuffix-list- 100% | 0.0 B/s | 68.3 KiB | 00m00s [ 15/155] Installing libssh-config-0:0. 100% | 0.0 B/s | 816.0 B | 00m00s [ 16/155] Installing ncurses-base-0:6.4 100% | 85.8 MiB/s | 351.6 KiB | 00m00s [ 17/155] Installing glibc-minimal-lang 100% | 0.0 B/s | 124.0 B | 00m00s [ 18/155] Installing ncurses-libs-0:6.4 100% | 236.7 MiB/s | 969.7 KiB | 00m00s >>> Running pre-install scriptlet: glibc-0:2.39.9000-14.fc41.x86_64 >>> Stop pre-install scriptlet: glibc-0:2.39.9000-14.fc41.x86_64 [ 19/155] Installing glibc-0:2.39.9000- 100% | 231.7 MiB/s | 6.7 MiB | 00m00s >>> Running post-install scriptlet: glibc-0:2.39.9000-14.fc41.x86_64 >>> Stop post-install scriptlet: glibc-0:2.39.9000-14.fc41.x86_64 [ 20/155] Installing bash-0:5.2.26-3.fc 100% | 408.1 MiB/s | 8.2 MiB | 00m00s >>> Running post-install scriptlet: bash-0:5.2.26-3.fc40.x86_64 >>> Stop post-install scriptlet: bash-0:5.2.26-3.fc40.x86_64 [ 21/155] Installing glibc-common-0:2.3 100% | 205.5 MiB/s | 1.0 MiB | 00m00s [ 22/155] Installing glibc-gconv-extra- 100% | 253.7 MiB/s | 7.9 MiB | 00m00s >>> Running post-install scriptlet: glibc-gconv-extra-0:2.39.9000-14.fc41.x86_64 >>> Stop post-install scriptlet: glibc-gconv-extra-0:2.39.9000-14.fc41.x86_64 [ 23/155] Installing zlib-ng-compat-0:2 100% | 131.7 MiB/s | 134.8 KiB | 00m00s [ 24/155] Installing xz-libs-1:5.4.6-3. 100% | 206.0 MiB/s | 210.9 KiB | 00m00s [ 25/155] Installing bzip2-libs-0:1.0.8 100% | 0.0 B/s | 81.8 KiB | 00m00s [ 26/155] Installing readline-0:8.2-8.f 100% | 479.9 MiB/s | 491.4 KiB | 00m00s [ 27/155] Installing libuuid-0:2.40-13. 100% | 0.0 B/s | 38.5 KiB | 00m00s [ 28/155] Installing libzstd-0:1.5.6-1. 100% | 385.3 MiB/s | 789.2 KiB | 00m00s [ 29/155] Installing elfutils-libelf-0: 100% | 389.8 MiB/s | 1.2 MiB | 00m00s [ 30/155] Installing popt-0:1.19-6.fc40 100% | 70.1 MiB/s | 143.5 KiB | 00m00s [ 31/155] Installing libstdc++-0:14.0.1 100% | 394.6 MiB/s | 2.8 MiB | 00m00s [ 32/155] Installing libblkid-0:2.40-13 100% | 257.5 MiB/s | 263.7 KiB | 00m00s [ 33/155] Installing libattr-0:2.5.2-3. 100% | 0.0 B/s | 29.5 KiB | 00m00s [ 34/155] Installing libacl-0:2.3.2-1.f 100% | 0.0 B/s | 40.8 KiB | 00m00s [ 35/155] Installing libxcrypt-0:4.4.36 100% | 259.3 MiB/s | 265.5 KiB | 00m00s [ 36/155] Installing gmp-1:6.3.0-1.fc41 100% | 393.4 MiB/s | 805.6 KiB | 00m00s [ 37/155] Installing libeconf-0:0.6.2-1 100% | 0.0 B/s | 59.6 KiB | 00m00s [ 38/155] Installing lz4-libs-0:1.9.4-6 100% | 0.0 B/s | 130.5 KiB | 00m00s [ 39/155] Installing gdbm-libs-1:1.23-6 100% | 120.7 MiB/s | 123.6 KiB | 00m00s [ 40/155] Installing mpfr-0:4.2.1-3.fc4 100% | 271.3 MiB/s | 833.5 KiB | 00m00s [ 41/155] Installing gawk-0:5.3.0-3.fc4 100% | 288.0 MiB/s | 1.7 MiB | 00m00s [ 42/155] Installing dwz-0:0.15-6.fc40. 100% | 285.5 MiB/s | 292.3 KiB | 00m00s [ 43/155] Installing unzip-0:6.0-63.fc4 100% | 188.6 MiB/s | 386.3 KiB | 00m00s [ 44/155] Installing file-libs-0:5.45-5 100% | 709.3 MiB/s | 9.9 MiB | 00m00s [ 45/155] Installing file-0:5.45-5.fc41 100% | 102.6 MiB/s | 105.0 KiB | 00m00s [ 46/155] Installing libcap-ng-0:0.8.5- 100% | 0.0 B/s | 71.0 KiB | 00m00s [ 47/155] Installing audit-libs-0:4.0.1 100% | 321.7 MiB/s | 329.4 KiB | 00m00s [ 48/155] Installing pam-libs-0:1.6.1-1 100% | 134.2 MiB/s | 137.4 KiB | 00m00s [ 49/155] Installing libcap-0:2.69-8.fc 100% | 219.4 MiB/s | 224.7 KiB | 00m00s [ 50/155] Installing systemd-libs-0:255 100% | 385.3 MiB/s | 1.9 MiB | 00m00s [ 51/155] Installing libsmartcols-0:2.4 100% | 177.3 MiB/s | 181.5 KiB | 00m00s [ 52/155] Installing lua-libs-0:5.4.6-5 100% | 275.7 MiB/s | 282.3 KiB | 00m00s [ 53/155] Installing libsepol-0:3.6-3.f 100% | 392.1 MiB/s | 803.0 KiB | 00m00s [ 54/155] Installing libcom_err-0:1.47. 100% | 0.0 B/s | 68.3 KiB | 00m00s [ 55/155] Installing alternatives-0:1.2 100% | 0.0 B/s | 64.0 KiB | 00m00s [ 56/155] Installing jansson-0:2.13.1-9 100% | 87.6 MiB/s | 89.7 KiB | 00m00s [ 57/155] Installing libtasn1-0:4.19.0- 100% | 173.3 MiB/s | 177.5 KiB | 00m00s [ 58/155] Installing libunistring-0:1.1 100% | 432.7 MiB/s | 1.7 MiB | 00m00s [ 59/155] Installing libidn2-0:2.3.7-1. 100% | 163.6 MiB/s | 335.0 KiB | 00m00s [ 60/155] Installing libpsl-0:0.21.5-3. 100% | 0.0 B/s | 81.6 KiB | 00m00s [ 61/155] Installing zip-0:3.0-40.fc40. 100% | 345.3 MiB/s | 707.1 KiB | 00m00s [ 62/155] Installing gdbm-1:1.23-6.fc40 100% | 227.4 MiB/s | 465.8 KiB | 00m00s [ 63/155] Installing cyrus-sasl-lib-0:2 100% | 380.5 MiB/s | 2.3 MiB | 00m00s [ 64/155] Installing zstd-0:1.5.6-1.fc4 100% | 419.0 MiB/s | 1.7 MiB | 00m00s [ 65/155] Installing libfdisk-0:2.40-13 100% | 355.4 MiB/s | 363.9 KiB | 00m00s [ 66/155] Installing bzip2-0:1.0.8-18.f 100% | 93.9 MiB/s | 96.2 KiB | 00m00s [ 67/155] Installing libxml2-0:2.12.6-1 100% | 340.0 MiB/s | 1.7 MiB | 00m00s [ 68/155] Installing sqlite-libs-0:3.45 100% | 351.3 MiB/s | 1.4 MiB | 00m00s [ 69/155] Installing ed-0:1.20.2-1.fc41 100% | 145.7 MiB/s | 149.2 KiB | 00m00s [ 70/155] Installing elfutils-default-y 100% | 408.6 KiB/s | 2.0 KiB | 00m00s >>> Running post-install scriptlet: elfutils-default-yama-scope-0:0.191-7.fc41.n >>> Stop post-install scriptlet: elfutils-default-yama-scope-0:0.191-7.fc41.noar [ 71/155] Installing cpio-0:2.15-1.fc40 100% | 274.9 MiB/s | 1.1 MiB | 00m00s [ 72/155] Installing diffutils-0:3.10-5 100% | 317.2 MiB/s | 1.6 MiB | 00m00s [ 73/155] Installing libgomp-0:14.0.1-0 100% | 508.4 MiB/s | 520.6 KiB | 00m00s [ 74/155] Installing libpkgconf-0:2.1.0 100% | 0.0 B/s | 75.3 KiB | 00m00s [ 75/155] Installing pkgconf-0:2.1.0-1. 100% | 82.9 MiB/s | 84.9 KiB | 00m00s [ 76/155] Installing keyutils-libs-0:1. 100% | 0.0 B/s | 55.8 KiB | 00m00s [ 77/155] Installing libverto-0:0.3.2-8 100% | 0.0 B/s | 31.3 KiB | 00m00s [ 78/155] Installing libffi-0:3.4.6-1.f 100% | 81.8 MiB/s | 83.8 KiB | 00m00s [ 79/155] Installing p11-kit-0:0.25.3-4 100% | 274.3 MiB/s | 2.2 MiB | 00m00s [ 80/155] Installing p11-kit-trust-0:0. 100% | 54.8 MiB/s | 393.1 KiB | 00m00s >>> Running post-install scriptlet: p11-kit-trust-0:0.25.3-4.fc40.x86_64 >>> Stop post-install scriptlet: p11-kit-trust-0:0.25.3-4.fc40.x86_64 [ 81/155] Installing xxhash-libs-0:0.8. 100% | 87.8 MiB/s | 89.9 KiB | 00m00s [ 82/155] Installing libbrotli-0:1.1.0- 100% | 270.8 MiB/s | 831.9 KiB | 00m00s [ 83/155] Installing libnghttp2-0:1.61. 100% | 163.3 MiB/s | 167.2 KiB | 00m00s [ 84/155] Installing libtool-ltdl-0:2.4 100% | 0.0 B/s | 67.3 KiB | 00m00s [ 85/155] Installing pcre2-syntax-0:10. 100% | 245.6 MiB/s | 251.5 KiB | 00m00s [ 86/155] Installing pcre2-0:10.43-1.fc 100% | 319.8 MiB/s | 654.9 KiB | 00m00s [ 87/155] Installing libselinux-0:3.6-5 100% | 174.1 MiB/s | 178.3 KiB | 00m00s [ 88/155] Installing sed-0:4.9-1.fc40.x 100% | 212.3 MiB/s | 869.7 KiB | 00m00s [ 89/155] Installing grep-0:3.11-7.fc40 100% | 250.8 MiB/s | 1.0 MiB | 00m00s [ 90/155] Installing findutils-1:4.9.0- 100% | 293.2 MiB/s | 1.5 MiB | 00m00s [ 91/155] Installing xz-1:5.4.6-3.fc41. 100% | 286.1 MiB/s | 2.0 MiB | 00m00s [ 92/155] Installing libmount-0:2.40-13 100% | 344.6 MiB/s | 352.9 KiB | 00m00s [ 93/155] Installing util-linux-core-0: 100% | 247.3 MiB/s | 1.5 MiB | 00m00s [ 94/155] Installing patch-0:2.7.6-24.f 100% | 258.1 MiB/s | 264.3 KiB | 00m00s [ 95/155] Installing tar-2:1.35-3.fc40. 100% | 368.8 MiB/s | 3.0 MiB | 00m00s [ 96/155] Installing libsemanage-0:3.6- 100% | 144.2 MiB/s | 295.3 KiB | 00m00s [ 97/155] Installing shadow-utils-2:4.1 100% | 166.8 MiB/s | 4.2 MiB | 00m00s >>> Running pre-install scriptlet: libutempter-0:1.2.1-13.fc40.x86_64 >>> Stop pre-install scriptlet: libutempter-0:1.2.1-13.fc40.x86_64 [ 98/155] Installing libutempter-0:1.2. 100% | 58.3 MiB/s | 59.7 KiB | 00m00s [ 99/155] Installing pkgconf-m4-0:2.1.0 100% | 0.0 B/s | 14.3 KiB | 00m00s [100/155] Installing pkgconf-pkg-config 100% | 0.0 B/s | 1.8 KiB | 00m00s [101/155] Installing coreutils-common-0 100% | 414.4 MiB/s | 11.2 MiB | 00m00s [102/155] Installing openssl-libs-1:3.2 100% | 458.6 MiB/s | 7.8 MiB | 00m00s [103/155] Installing coreutils-0:9.5-1. 100% | 294.2 MiB/s | 5.6 MiB | 00m00s >>> Running pre-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.n >>> Stop pre-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.noar [104/155] Installing ca-certificates-0: 100% | 4.1 MiB/s | 2.3 MiB | 00m01s >>> Running post-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40. >>> Stop post-install scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40.noa [105/155] Installing krb5-libs-0:1.21.2 100% | 286.8 MiB/s | 2.3 MiB | 00m00s [106/155] Installing libtirpc-0:1.3.4-1 100% | 199.8 MiB/s | 204.6 KiB | 00m00s [107/155] Installing gzip-0:1.13-1.fc40 100% | 190.7 MiB/s | 390.6 KiB | 00m00s [108/155] Installing authselect-libs-0: 100% | 203.4 MiB/s | 833.2 KiB | 00m00s [109/155] Installing libarchive-0:3.7.2 100% | 298.4 MiB/s | 916.6 KiB | 00m00s [110/155] Installing authselect-0:1.5.0 100% | 154.2 MiB/s | 157.9 KiB | 00m00s [111/155] Installing cracklib-0:2.9.11- 100% | 81.5 MiB/s | 250.3 KiB | 00m00s [112/155] Installing libpwquality-0:1.4 100% | 105.0 MiB/s | 430.1 KiB | 00m00s [113/155] Installing libnsl2-0:2.0.1-1. 100% | 57.7 MiB/s | 59.0 KiB | 00m00s [114/155] Installing pam-0:1.6.1-1.fc41 100% | 165.0 MiB/s | 1.8 MiB | 00m00s [115/155] Installing libssh-0:0.10.6-6. 100% | 251.7 MiB/s | 515.4 KiB | 00m00s [116/155] Installing rpm-sequoia-0:1.6. 100% | 371.5 MiB/s | 2.2 MiB | 00m00s [117/155] Installing rpm-libs-0:4.19.1. 100% | 231.6 MiB/s | 711.4 KiB | 00m00s [118/155] Installing libevent-0:2.1.12- 100% | 292.8 MiB/s | 899.4 KiB | 00m00s [119/155] Installing openldap-0:2.6.7-1 100% | 208.0 MiB/s | 638.9 KiB | 00m00s [120/155] Installing libcurl-0:8.7.1-1. 100% | 258.7 MiB/s | 794.6 KiB | 00m00s [121/155] Installing elfutils-libs-0:0. 100% | 316.4 MiB/s | 648.0 KiB | 00m00s [122/155] Installing elfutils-debuginfo 100% | 65.3 MiB/s | 66.9 KiB | 00m00s [123/155] Installing binutils-0:2.42.50 100% | 400.7 MiB/s | 27.2 MiB | 00m00s >>> Running post-install scriptlet: binutils-0:2.42.50-6.fc41.x86_64 >>> Stop post-install scriptlet: binutils-0:2.42.50-6.fc41.x86_64 [124/155] Installing binutils-gold-0:2. 100% | 184.6 MiB/s | 2.0 MiB | 00m00s >>> Running post-install scriptlet: binutils-gold-0:2.42.50-6.fc41.x86_64 >>> Stop post-install scriptlet: binutils-gold-0:2.42.50-6.fc41.x86_64 [125/155] Installing elfutils-0:0.191-7 100% | 364.6 MiB/s | 2.6 MiB | 00m00s [126/155] Installing gdb-minimal-0:14.2 100% | 421.9 MiB/s | 12.7 MiB | 00m00s [127/155] Installing debugedit-0:5.0-14 100% | 197.0 MiB/s | 201.7 KiB | 00m00s [128/155] Installing rpm-build-libs-0:4 100% | 194.6 MiB/s | 199.2 KiB | 00m00s [129/155] Installing curl-0:8.7.1-1.fc4 100% | 82.5 MiB/s | 760.6 KiB | 00m00s >>> Running pre-install scriptlet: rpm-0:4.19.1.1-1.fc41.x86_64 >>> Stop pre-install scriptlet: rpm-0:4.19.1.1-1.fc41.x86_64 [130/155] Installing rpm-0:4.19.1.1-1.f 100% | 171.2 MiB/s | 2.4 MiB | 00m00s [131/155] Installing efi-srpm-macros-0: 100% | 0.0 B/s | 41.2 KiB | 00m00s [132/155] Installing lua-srpm-macros-0: 100% | 0.0 B/s | 1.9 KiB | 00m00s [133/155] Installing zig-srpm-macros-0: 100% | 0.0 B/s | 1.7 KiB | 00m00s [134/155] Installing rust-srpm-macros-0 100% | 0.0 B/s | 5.6 KiB | 00m00s [135/155] Installing qt6-srpm-macros-0: 100% | 0.0 B/s | 732.0 B | 00m00s [136/155] Installing qt5-srpm-macros-0: 100% | 0.0 B/s | 768.0 B | 00m00s [137/155] Installing perl-srpm-macros-0 100% | 0.0 B/s | 1.1 KiB | 00m00s [138/155] Installing package-notes-srpm 100% | 0.0 B/s | 2.0 KiB | 00m00s [139/155] Installing openblas-srpm-macr 100% | 0.0 B/s | 392.0 B | 00m00s [140/155] Installing ocaml-srpm-macros- 100% | 0.0 B/s | 2.2 KiB | 00m00s [141/155] Installing kernel-srpm-macros 100% | 0.0 B/s | 2.3 KiB | 00m00s [142/155] Installing gnat-srpm-macros-0 100% | 0.0 B/s | 1.3 KiB | 00m00s [143/155] Installing ghc-srpm-macros-0: 100% | 0.0 B/s | 1.0 KiB | 00m00s [144/155] Installing fpc-srpm-macros-0: 100% | 0.0 B/s | 420.0 B | 00m00s [145/155] Installing ansible-srpm-macro 100% | 0.0 B/s | 36.2 KiB | 00m00s [146/155] Installing fonts-srpm-macros- 100% | 0.0 B/s | 56.5 KiB | 00m00s [147/155] Installing forge-srpm-macros- 100% | 0.0 B/s | 40.3 KiB | 00m00s [148/155] Installing go-srpm-macros-0:3 100% | 0.0 B/s | 62.0 KiB | 00m00s [149/155] Installing python-srpm-macros 100% | 0.0 B/s | 51.3 KiB | 00m00s [150/155] Installing redhat-rpm-config- 100% | 92.6 MiB/s | 189.7 KiB | 00m00s [151/155] Installing rpm-build-0:4.19.1 100% | 88.8 MiB/s | 182.0 KiB | 00m00s [152/155] Installing pyproject-srpm-mac 100% | 2.0 MiB/s | 2.1 KiB | 00m00s [153/155] Installing util-linux-0:2.40- 100% | 178.0 MiB/s | 3.7 MiB | 00m00s >>> Running post-install scriptlet: util-linux-0:2.40-13.fc41.x86_64 >>> Stop post-install scriptlet: util-linux-0:2.40-13.fc41.x86_64 [154/155] Installing which-0:2.21-41.fc 100% | 80.5 MiB/s | 82.4 KiB | 00m00s [155/155] Installing info-0:7.1-2.fc40. 100% | 438.9 KiB/s | 358.2 KiB | 00m01s >>> Running post-transaction scriptlet: filesystem-0:3.18-9.fc41.x86_64 >>> Stop post-transaction scriptlet: filesystem-0:3.18-9.fc41.x86_64 >>> Running post-transaction scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.f >>> Stop post-transaction scriptlet: ca-certificates-0:2023.2.62_v7.0.401-6.fc40 >>> Running post-transaction scriptlet: authselect-libs-0:1.5.0-5.fc41.x86_64 >>> Stop post-transaction scriptlet: authselect-libs-0:1.5.0-5.fc41.x86_64 >>> Running post-transaction scriptlet: rpm-0:4.19.1.1-1.fc41.x86_64 >>> Stop post-transaction scriptlet: rpm-0:4.19.1.1-1.fc41.x86_64 >>> Running trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 >>> Stop trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 >>> Running trigger-install scriptlet: info-0:7.1-2.fc40.x86_64 >>> Stop trigger-install scriptlet: info-0:7.1-2.fc40.x86_64 Warning: skipped PGP checks for 153 package(s). Finish: installing minimal buildroot with dnf5 Start: creating root cache Finish: creating root cache Finish: chroot init INFO: Installed packages: INFO: alternatives-1.26-3.fc40.x86_64 ansible-srpm-macros-1-15.fc41.noarch audit-libs-4.0.1-1.fc41.x86_64 authselect-1.5.0-5.fc41.x86_64 authselect-libs-1.5.0-5.fc41.x86_64 basesystem-11-20.fc40.noarch bash-5.2.26-3.fc40.x86_64 binutils-2.42.50-6.fc41.x86_64 binutils-gold-2.42.50-6.fc41.x86_64 bzip2-1.0.8-18.fc40.x86_64 bzip2-libs-1.0.8-18.fc40.x86_64 ca-certificates-2023.2.62_v7.0.401-6.fc40.noarch coreutils-9.5-1.fc41.x86_64 coreutils-common-9.5-1.fc41.x86_64 cpio-2.15-1.fc40.x86_64 cracklib-2.9.11-5.fc40.x86_64 crypto-policies-20240320-1.git58e3d95.fc41.noarch curl-8.7.1-1.fc41.x86_64 cyrus-sasl-lib-2.1.28-19.fc40.x86_64 debugedit-5.0-14.fc40.x86_64 diffutils-3.10-5.fc40.x86_64 dwz-0.15-6.fc40.x86_64 ed-1.20.2-1.fc41.x86_64 efi-srpm-macros-5-11.fc40.noarch elfutils-0.191-7.fc41.x86_64 elfutils-debuginfod-client-0.191-7.fc41.x86_64 elfutils-default-yama-scope-0.191-7.fc41.noarch elfutils-libelf-0.191-7.fc41.x86_64 elfutils-libs-0.191-7.fc41.x86_64 fedora-gpg-keys-41-0.1.noarch fedora-release-41-0.9.noarch fedora-release-common-41-0.9.noarch fedora-release-identity-basic-41-0.9.noarch fedora-repos-41-0.1.noarch fedora-repos-rawhide-41-0.1.noarch file-5.45-5.fc41.x86_64 file-libs-5.45-5.fc41.x86_64 filesystem-3.18-9.fc41.x86_64 findutils-4.9.0-8.fc40.x86_64 fonts-srpm-macros-2.0.5-14.fc40.noarch forge-srpm-macros-0.3.1-1.fc41.noarch fpc-srpm-macros-1.3-12.fc40.noarch gawk-5.3.0-3.fc40.x86_64 gdb-minimal-14.2-5.fc41.x86_64 gdbm-1.23-6.fc40.x86_64 gdbm-libs-1.23-6.fc40.x86_64 ghc-srpm-macros-1.9.1-1.fc41.noarch glibc-2.39.9000-14.fc41.x86_64 glibc-common-2.39.9000-14.fc41.x86_64 glibc-gconv-extra-2.39.9000-14.fc41.x86_64 glibc-minimal-langpack-2.39.9000-14.fc41.x86_64 gmp-6.3.0-1.fc41.x86_64 gnat-srpm-macros-6-5.fc40.noarch go-srpm-macros-3.6.0-1.fc41.noarch grep-3.11-7.fc40.x86_64 gzip-1.13-1.fc40.x86_64 info-7.1-2.fc40.x86_64 jansson-2.13.1-9.fc40.x86_64 kernel-srpm-macros-1.0-23.fc41.noarch keyutils-libs-1.6.3-3.fc40.x86_64 krb5-libs-1.21.2-5.fc40.x86_64 libacl-2.3.2-1.fc40.x86_64 libarchive-3.7.2-3.fc41.x86_64 libattr-2.5.2-3.fc40.x86_64 libblkid-2.40-13.fc41.x86_64 libbrotli-1.1.0-3.fc41.x86_64 libcap-2.69-8.fc41.x86_64 libcap-ng-0.8.5-1.fc41.x86_64 libcom_err-1.47.0-5.fc40.x86_64 libcurl-8.7.1-1.fc41.x86_64 libeconf-0.6.2-1.fc41.x86_64 libevent-2.1.12-12.fc40.x86_64 libfdisk-2.40-13.fc41.x86_64 libffi-3.4.6-1.fc41.x86_64 libgcc-14.0.1-0.15.fc41.x86_64 libgomp-14.0.1-0.15.fc41.x86_64 libidn2-2.3.7-1.fc40.x86_64 libmount-2.40-13.fc41.x86_64 libnghttp2-1.61.0-1.fc41.x86_64 libnsl2-2.0.1-1.fc40.x86_64 libpkgconf-2.1.0-1.fc40.x86_64 libpsl-0.21.5-3.fc40.x86_64 libpwquality-1.4.5-9.fc41.x86_64 libselinux-3.6-5.fc41.x86_64 libsemanage-3.6-3.fc41.x86_64 libsepol-3.6-3.fc40.x86_64 libsmartcols-2.40-13.fc41.x86_64 libssh-0.10.6-6.fc41.x86_64 libssh-config-0.10.6-6.fc41.noarch libstdc++-14.0.1-0.15.fc41.x86_64 libtasn1-4.19.0-6.fc40.x86_64 libtirpc-1.3.4-1.rc3.fc41.x86_64 libtool-ltdl-2.4.7-10.fc40.x86_64 libunistring-1.1-7.fc41.x86_64 libutempter-1.2.1-13.fc40.x86_64 libuuid-2.40-13.fc41.x86_64 libverto-0.3.2-8.fc40.x86_64 libxcrypt-4.4.36-5.fc40.x86_64 libxml2-2.12.6-1.fc41.x86_64 libzstd-1.5.6-1.fc41.x86_64 lua-libs-5.4.6-5.fc40.x86_64 lua-srpm-macros-1-13.fc40.noarch lz4-libs-1.9.4-6.fc40.x86_64 mpfr-4.2.1-3.fc40.x86_64 ncurses-base-6.4-12.20240127.fc40.noarch ncurses-libs-6.4-12.20240127.fc40.x86_64 ocaml-srpm-macros-9-3.fc40.noarch openblas-srpm-macros-2-17.fc41.noarch openldap-2.6.7-1.fc40.x86_64 openssl-libs-3.2.1-6.fc41.x86_64 p11-kit-0.25.3-4.fc40.x86_64 p11-kit-trust-0.25.3-4.fc40.x86_64 package-notes-srpm-macros-0.5-11.fc40.noarch pam-1.6.1-1.fc41.x86_64 pam-libs-1.6.1-1.fc41.x86_64 patch-2.7.6-24.fc40.x86_64 pcre2-10.43-1.fc41.x86_64 pcre2-syntax-10.43-1.fc41.noarch perl-srpm-macros-1-53.fc40.noarch pkgconf-2.1.0-1.fc40.x86_64 pkgconf-m4-2.1.0-1.fc40.noarch pkgconf-pkg-config-2.1.0-1.fc40.x86_64 popt-1.19-6.fc40.x86_64 publicsuffix-list-dafsa-20240107-3.fc40.noarch pyproject-srpm-macros-1.12.0-1.fc40.noarch python-srpm-macros-3.13-5.fc40.noarch qt5-srpm-macros-5.15.13-1.fc41.noarch qt6-srpm-macros-6.7.0-1.fc41.noarch readline-8.2-8.fc40.x86_64 redhat-rpm-config-288-1.fc41.noarch rpm-4.19.1.1-1.fc41.x86_64 rpm-build-4.19.1.1-1.fc41.x86_64 rpm-build-libs-4.19.1.1-1.fc41.x86_64 rpm-libs-4.19.1.1-1.fc41.x86_64 rpm-sequoia-1.6.0-2.fc40.x86_64 rust-srpm-macros-26.2-1.fc41.noarch sed-4.9-1.fc40.x86_64 setup-2.14.5-2.fc40.noarch shadow-utils-4.15.1-2.fc41.x86_64 sqlite-libs-3.45.2-1.fc41.x86_64 systemd-libs-255.5-1.fc41.x86_64 tar-1.35-3.fc40.x86_64 unzip-6.0-63.fc40.x86_64 util-linux-2.40-13.fc41.x86_64 util-linux-core-2.40-13.fc41.x86_64 which-2.21-41.fc40.x86_64 xxhash-libs-0.8.2-2.fc40.x86_64 xz-5.4.6-3.fc41.x86_64 xz-libs-5.4.6-3.fc41.x86_64 zig-srpm-macros-1-2.fc40.noarch zip-3.0-40.fc40.x86_64 zlib-ng-compat-2.1.6-2.fc40.x86_64 zstd-1.5.6-1.fc41.x86_64 Start: buildsrpm Start: rpmbuild -bs Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.src.rpm Finish: rpmbuild -bs cp: preserving permissions for ‘/var/lib/copr-rpmbuild/results/chroot_scan/var/lib/mock/fedora-rawhide-x86_64-1714048811.076583/root/var/log’: No such file or directory INFO: chroot_scan: 1 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-rawhide-x86_64-1714048811.076583/root/var/log/dnf5.log Finish: buildsrpm INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-a3xghms3/python-django-mailman3/python-django-mailman3.spec) Config(child) 0 minutes 15 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.11-2.fc41.src.rpm) Config(fedora-rawhide-x86_64) Start: chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1714048811.076583/root. INFO: calling preinit hooks INFO: enabled root cache Start: unpacking root cache Finish: unpacking root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin INFO: Buildroot is handled by package management from host and used with --installroot: rpm-4.19.1.1-1.fc39.x86_64 rpm-sequoia-1.6.0-1.fc39.x86_64 python3-dnf-4.19.2-1.fc39.noarch python3-dnf-plugins-core-4.6.0-1.fc39.noarch yum-4.19.2-1.fc39.noarch dnf5-5.1.17-1.fc39.x86_64 dnf5-plugins-5.1.17-1.fc39.x86_64 Finish: chroot init Start: build phase for python-django-mailman3-1.3.11-2.fc41.src.rpm Start: build setup for python-django-mailman3-1.3.11-2.fc41.src.rpm Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.src.rpm Updating and loading repositories: fedora 100% | 214.2 KiB/s | 19.9 KiB | 00m00s Additional repo http_kojipkgs_fedorapr 100% | 17.9 KiB/s | 4.1 KiB | 00m00s Copr repository 100% | 73.2 KiB/s | 1.5 KiB | 00m00s Repositories loaded. Package Arch Version Repository Size Installing: python3-devel x86_64 3.13.0~a6-2.1.fc41 copr_base 1.5 MiB python3-setuptools noarch 69.1.1-2.fc41~bootstrap copr_base 7.2 MiB Installing dependencies: expat x86_64 2.6.2-1.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 280.8 KiB libb2 x86_64 0.98.1-11.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 42.2 KiB mpdecimal x86_64 2.5.1-9.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 200.9 KiB pyproject-rpm-macros noarch 1.12.0-1.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 98.8 KiB python-pip-wheel noarch 24.0-2.fc41 copr_base 1.5 MiB python-rpm-macros noarch 3.13-5.fc40 copr_base 22.1 KiB python3 x86_64 3.13.0~a6-2.1.fc41 copr_base 31.8 KiB python3-libs x86_64 3.13.0~a6-2.1.fc41 copr_base 38.5 MiB python3-packaging noarch 24.0-1.fc41 copr_base 425.3 KiB python3-rpm-generators noarch 14-10.fc40 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 81.7 KiB python3-rpm-macros noarch 3.13-5.fc40 copr_base 6.4 KiB tzdata noarch 2024a-5.fc41 http_kojipkgs_fedoraproject_org_repos_rawhide_latest_basearch 1.6 MiB Transaction Summary: Installing: 14 packages Total size of inbound packages is 12 MiB. Need to download 12 MiB. After this operation 52 MiB will be used (install 52 MiB, remove 0 B). [ 1/14] python3-0:3.13.0~a6-2.1.fc41.x8 100% | 1.5 MiB/s | 26.0 KiB | 00m00s [ 2/14] python3-setuptools-0:69.1.1-2.f 100% | 72.4 MiB/s | 1.4 MiB | 00m00s [ 3/14] python3-devel-0:3.13.0~a6-2.1.f 100% | 14.1 MiB/s | 318.7 KiB | 00m00s [ 4/14] python-rpm-macros-0:3.13-5.fc40 100% | 9.6 MiB/s | 19.6 KiB | 00m00s [ 5/14] python3-rpm-macros-0:3.13-5.fc4 100% | 7.0 MiB/s | 14.3 KiB | 00m00s [ 6/14] python3-libs-0:3.13.0~a6-2.1.fc 100% | 61.9 MiB/s | 8.4 MiB | 00m00s [ 7/14] libb2-0:0.98.1-11.fc40.x86_64 100% | 197.4 KiB/s | 25.5 KiB | 00m00s [ 8/14] python-pip-wheel-0:24.0-2.fc41. 100% | 184.5 MiB/s | 1.5 MiB | 00m00s [ 9/14] expat-0:2.6.2-1.fc41.x86_64 100% | 797.2 KiB/s | 113.2 KiB | 00m00s [10/14] mpdecimal-0:2.5.1-9.fc40.x86_64 100% | 1.6 MiB/s | 88.6 KiB | 00m00s [11/14] tzdata-0:2024a-5.fc41.noarch 100% | 7.1 MiB/s | 431.3 KiB | 00m00s [12/14] python3-packaging-0:24.0-1.fc41 100% | 58.0 MiB/s | 118.8 KiB | 00m00s [13/14] python3-rpm-generators-0:14-10. 100% | 1.2 MiB/s | 29.6 KiB | 00m00s [14/14] pyproject-rpm-macros-0:1.12.0-1 100% | 308.7 KiB/s | 41.4 KiB | 00m00s -------------------------------------------------------------------------------- [14/14] Total 100% | 41.5 MiB/s | 12.5 MiB | 00m00s Running transaction [ 1/16] Verify package files 100% | 297.0 B/s | 14.0 B | 00m00s [ 2/16] Prepare transaction 100% | 583.0 B/s | 14.0 B | 00m00s [ 3/16] Installing python-rpm-macros-0: 100% | 0.0 B/s | 22.8 KiB | 00m00s [ 4/16] Installing python3-rpm-macros-0 100% | 0.0 B/s | 6.7 KiB | 00m00s [ 5/16] Installing pyproject-rpm-macros 100% | 49.2 MiB/s | 100.8 KiB | 00m00s [ 6/16] Installing tzdata-0:2024a-5.fc4 100% | 67.9 MiB/s | 1.9 MiB | 00m00s [ 7/16] Installing python-pip-wheel-0:2 100% | 764.0 MiB/s | 1.5 MiB | 00m00s [ 8/16] Installing mpdecimal-0:2.5.1-9. 100% | 197.3 MiB/s | 202.0 KiB | 00m00s [ 9/16] Installing libb2-0:0.98.1-11.fc 100% | 0.0 B/s | 43.3 KiB | 00m00s [10/16] Installing expat-0:2.6.2-1.fc41 100% | 69.1 MiB/s | 282.9 KiB | 00m00s [11/16] Installing python3-libs-0:3.13. 100% | 360.0 MiB/s | 38.9 MiB | 00m00s [12/16] Installing python3-0:3.13.0~a6- 100% | 0.0 B/s | 33.6 KiB | 00m00s [13/16] Installing python3-packaging-0: 100% | 142.0 MiB/s | 436.1 KiB | 00m00s [14/16] Installing python3-rpm-generato 100% | 81.0 MiB/s | 82.9 KiB | 00m00s [15/16] Installing python3-devel-0:3.13 100% | 198.6 MiB/s | 1.6 MiB | 00m00s [16/16] Installing python3-setuptools-0 100% | 83.2 MiB/s | 7.3 MiB | 00m00s >>> Running trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 >>> Stop trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 Warning: skipped PGP checks for 14 package(s). Finish: build setup for python-django-mailman3-1.3.11-2.fc41.src.rpm Start: rpmbuild python-django-mailman3-1.3.11-2.fc41.src.rpm Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.0j1q9e + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-mailman3-1.3.11 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-mailman3-1.3.11.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-mailman3-1.3.11 + rm -rf /builddir/build/BUILD/django-mailman3-1.3.11-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/django-mailman3-1.3.11-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-fedora-oidc.patch + /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.lRKpuD + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + RPM_TOXENV=py313 + 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.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.1.1) 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.11-2.fc41.x86_64-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires Updating and loading repositories: Additional repo http_kojipkgs_fedorapr 100% | 72.4 KiB/s | 4.1 KiB | 00m00s fedora 100% | 147.5 KiB/s | 19.9 KiB | 00m00s Copr repository 100% | 76.9 KiB/s | 1.5 KiB | 00m00s Repositories loaded. Package Arch Version Repository Size Installing: python3-pip noarch 24.0-2.fc41 copr_base 14.2 MiB python3-wheel noarch 1:0.43.0-1.fc41 copr_base 516.0 KiB Transaction Summary: Installing: 2 packages Total size of inbound packages is 3 MiB. Need to download 3 MiB. After this operation 15 MiB will be used (install 15 MiB, remove 0 B). Package "pyproject-rpm-macros-1.12.0-1.fc40.noarch" is already installed. Package "python3-devel-3.13.0~a6-2.1.fc41.x86_64" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "python3-packaging-24.0-1.fc41.noarch" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. [1/2] python3-wheel-1:0.43.0-1.fc41.noa 100% | 9.9 MiB/s | 151.3 KiB | 00m00s [2/2] python3-pip-0:24.0-2.fc41.noarch 100% | 95.7 MiB/s | 3.0 MiB | 00m00s -------------------------------------------------------------------------------- [2/2] Total 100% | 100.4 MiB/s | 3.1 MiB | 00m00s Running transaction [1/4] Verify package files 100% | 166.0 B/s | 2.0 B | 00m00s [2/4] Prepare transaction 100% | 142.0 B/s | 2.0 B | 00m00s [3/4] Installing python3-wheel-1:0.43.0 100% | 87.1 MiB/s | 535.0 KiB | 00m00s [4/4] Installing python3-pip-0:24.0-2.f 100% | 156.6 MiB/s | 14.6 MiB | 00m00s >>> Running trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 >>> Stop trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 Warning: skipped PGP checks for 2 package(s). Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.neXxLh + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + RPM_TOXENV=py313 + 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.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.1.1) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.43.0) 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.43.0) 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.11-2.fc41.x86_64-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires Updating and loading repositories: fedora 100% | 167.4 KiB/s | 19.9 KiB | 00m00s Copr repository 100% | 76.9 KiB/s | 1.5 KiB | 00m00s Additional repo http_kojipkgs_fedorapr 100% | 75.0 KiB/s | 4.1 KiB | 00m00s Repositories loaded. Package "pyproject-rpm-macros-1.12.0-1.fc40.noarch" is already installed. Package "python3-devel-3.13.0~a6-2.1.fc41.x86_64" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "python3-packaging-24.0-1.fc41.noarch" is already installed. Package "python3-pip-24.0-2.fc41.noarch" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "python3-wheel-1:0.43.0-1.fc41.noarch" is already installed. Package Arch Version Repository Size Installing: python3-tox-current-env noarch 0.0.11-9.fc41 copr_base 70.4 KiB Installing dependencies: python-setuptools-wheel noarch 68.2.2-1.fc40 copr_base 737.0 KiB python-wheel-wheel noarch 1:0.43.0-1.fc41 copr_base 65.1 KiB python3-cachetools noarch 5.3.3-1.fc41 copr_base 143.8 KiB python3-chardet noarch 5.2.0-8.fc41 copr_base 2.1 MiB python3-colorama noarch 0.4.6-7.fc41 copr_base 191.6 KiB python3-distlib noarch 0.3.8-1.fc41 copr_base 1.2 MiB python3-filelock noarch 3.13.4-1.fc41 copr_base 57.6 KiB python3-platformdirs noarch 3.11.0-3.fc41 copr_base 162.2 KiB python3-pluggy noarch 1.3.0-3.fc41 copr_base 183.1 KiB python3-pyproject-api noarch 1.6.1-3.fc41 copr_base 80.6 KiB python3-virtualenv noarch 20.21.1-18.fc41 copr_base 692.3 KiB tox noarch 4.14.2-1.fc41 copr_base 1.1 MiB Transaction Summary: Installing: 13 packages Total size of inbound packages is 2 MiB. Need to download 2 MiB. After this operation 7 MiB will be used (install 7 MiB, remove 0 B). [ 1/13] python3-tox-current-env-0:0.0.1 100% | 2.0 MiB/s | 30.4 KiB | 00m00s [ 2/13] python3-cachetools-0:5.3.3-1.fc 100% | 2.3 MiB/s | 38.0 KiB | 00m00s [ 3/13] python3-colorama-0:0.4.6-7.fc41 100% | 31.1 MiB/s | 63.6 KiB | 00m00s [ 4/13] tox-0:4.14.2-1.fc41.noarch 100% | 17.0 MiB/s | 348.0 KiB | 00m00s [ 5/13] python3-chardet-0:5.2.0-8.fc41. 100% | 53.6 MiB/s | 274.4 KiB | 00m00s [ 6/13] python3-filelock-0:3.13.4-1.fc4 100% | 15.2 MiB/s | 31.2 KiB | 00m00s [ 7/13] python3-platformdirs-0:3.11.0-3 100% | 13.2 MiB/s | 40.4 KiB | 00m00s [ 8/13] python3-pluggy-0:1.3.0-3.fc41.n 100% | 16.6 MiB/s | 51.0 KiB | 00m00s [ 9/13] python3-pyproject-api-0:1.6.1-3 100% | 9.2 MiB/s | 37.5 KiB | 00m00s [10/13] python3-virtualenv-0:20.21.1-18 100% | 62.6 MiB/s | 256.4 KiB | 00m00s [11/13] python3-distlib-0:0.3.8-1.fc41. 100% | 63.3 MiB/s | 259.4 KiB | 00m00s [12/13] python-setuptools-wheel-0:68.2. 100% | 108.8 MiB/s | 668.4 KiB | 00m00s [13/13] python-wheel-wheel-1:0.43.0-1.f 100% | 17.4 MiB/s | 71.4 KiB | 00m00s -------------------------------------------------------------------------------- [13/13] Total 100% | 64.2 MiB/s | 2.1 MiB | 00m00s Running transaction [ 1/15] Verify package files 100% | 1.4 KiB/s | 13.0 B | 00m00s [ 2/15] Prepare transaction 100% | 1.3 KiB/s | 13.0 B | 00m00s [ 3/15] Installing python3-platformdirs 100% | 82.5 MiB/s | 168.9 KiB | 00m00s [ 4/15] Installing python3-filelock-0:3 100% | 62.4 MiB/s | 63.9 KiB | 00m00s [ 5/15] Installing python-wheel-wheel-1 100% | 0.0 B/s | 65.8 KiB | 00m00s [ 6/15] Installing python-setuptools-wh 100% | 720.4 MiB/s | 737.7 KiB | 00m00s [ 7/15] Installing python3-distlib-0:0. 100% | 295.6 MiB/s | 1.2 MiB | 00m00s [ 8/15] Installing python3-virtualenv-0 100% | 83.0 MiB/s | 764.6 KiB | 00m00s [ 9/15] Installing python3-pyproject-ap 100% | 84.7 MiB/s | 86.8 KiB | 00m00s [10/15] Installing python3-pluggy-0:1.3 100% | 184.4 MiB/s | 188.8 KiB | 00m00s [11/15] Installing python3-colorama-0:0 100% | 98.4 MiB/s | 201.5 KiB | 00m00s [12/15] Installing python3-chardet-0:5. 100% | 299.0 MiB/s | 2.1 MiB | 00m00s [13/15] Installing python3-cachetools-0 100% | 144.3 MiB/s | 147.8 KiB | 00m00s [14/15] Installing tox-0:4.14.2-1.fc41. 100% | 133.8 MiB/s | 1.2 MiB | 00m00s [15/15] Installing python3-tox-current- 100% | 1.7 MiB/s | 74.7 KiB | 00m00s >>> Running trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 >>> Stop trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 Warning: skipped PGP checks for 13 package(s). Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.CdBBHK + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + RPM_TOXENV=py313 + 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.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.1.1) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.43.0) 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.43.0) 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) py313: OK (0.00 seconds) congratulations :) (0.04 seconds) Handling tox from tox --print-deps-only: py313 Requirement satisfied: tox (installed: tox 4.14.2) Handling mailmanclient from tox --print-deps-only: py313 Requirement not satisfied: mailmanclient Handling pytest-django from tox --print-deps-only: py313 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.11/django_mailman3-1.3.11.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 >=0.56 from hook generated metadata: Requires-Dist (django-mailman3) Requirement not satisfied: django-allauth >=0.56 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.11-2.fc41.x86_64-pyproject-buildrequires + rm -rfv django_mailman3-1.3.11.dist-info/ removed 'django_mailman3-1.3.11.dist-info/COPYING.txt' removed 'django_mailman3-1.3.11.dist-info/METADATA' removed 'django_mailman3-1.3.11.dist-info/top_level.txt' removed directory 'django_mailman3-1.3.11.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires Updating and loading repositories: Copr repository 100% | 96.1 KiB/s | 1.5 KiB | 00m00s fedora 100% | 74.0 KiB/s | 19.9 KiB | 00m00s Additional repo http_kojipkgs_fedorapr 100% | 60.6 KiB/s | 4.1 KiB | 00m00s Repositories loaded. Package "pyproject-rpm-macros-1.12.0-1.fc40.noarch" is already installed. Package "python3-devel-3.13.0~a6-2.1.fc41.x86_64" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "python3-packaging-24.0-1.fc41.noarch" is already installed. Package "python3-pip-24.0-2.fc41.noarch" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "tox-4.14.2-1.fc41.noarch" is already installed. Package "python3-tox-current-env-0.0.11-9.fc41.noarch" is already installed. Package "python3-wheel-1:0.43.0-1.fc41.noarch" is already installed. Package Arch Version Repository Size Installing: python3-django noarch 4.2.11-3.fc41 copr_base 20.5 MiB python3-django-allauth noarch 0.61.1-1.fc41 copr_base 5.2 MiB python3-django-gravatar2 noarch 1.4.4-9.fc41 copr_base 35.6 KiB python3-mailmanclient noarch 3.3.3-10.fc41 copr_base 983.1 KiB python3-pytest-django noarch 4.8.0-1.fc41 copr_base 145.0 KiB python3-pytz noarch 2024.1-1.fc41 copr_base 223.4 KiB Installing dependencies: python3-asgiref noarch 3.7.2-3.fc41 copr_base 176.2 KiB python3-cffi x86_64 1.16.0-4.fc41 copr_base 1.3 MiB python3-charset-normalizer noarch 3.3.2-3.fc41 copr_base 314.8 KiB python3-cryptography x86_64 42.0.5-1.fc41 copr_base 4.5 MiB python3-defusedxml noarch 0.7.1-13.fc41 copr_base 197.9 KiB python3-idna noarch 3.7-1.fc41 copr_base 595.7 KiB python3-iniconfig noarch 1.1.1-20.fc41 copr_base 20.5 KiB python3-jwt noarch 2.6.0-6.fc41 copr_base 143.3 KiB python3-jwt+crypto noarch 2.6.0-6.fc41 copr_base 5.3 KiB python3-oauthlib noarch 3.2.2-1.fc40 copr_base 988.9 KiB python3-openid noarch 3.1.0-21.fc41 copr_base 1.1 MiB python3-ply noarch 3.11-23.fc41 copr_base 569.3 KiB python3-pycparser noarch 2.20-16.fc41 copr_base 820.8 KiB python3-pytest noarch 7.4.3-3.fc41 copr_base 3.6 MiB python3-requests noarch 2.31.0-4.fc41 copr_base 462.0 KiB python3-requests-oauthlib noarch 1.3.1-8.fc41 copr_base 133.3 KiB python3-sqlparse noarch 0.4.2-9.fc41 copr_base 359.4 KiB python3-urllib3 noarch 1.26.18-4.fc41 copr_base 1.0 MiB Transaction Summary: Installing: 24 packages Total size of inbound packages is 10 MiB. Need to download 10 MiB. After this operation 43 MiB will be used (install 43 MiB, remove 0 B). [ 1/24] python3-django-gravatar2-0:1.4. 100% | 927.4 KiB/s | 24.1 KiB | 00m00s [ 2/24] python3-django-allauth-0:0.61.1 100% | 29.7 MiB/s | 1.1 MiB | 00m00s [ 3/24] python3-mailmanclient-0:3.3.3-1 100% | 11.9 MiB/s | 146.0 KiB | 00m00s [ 4/24] python3-pytest-django-0:4.8.0-1 100% | 5.4 MiB/s | 55.1 KiB | 00m00s [ 5/24] python3-pytz-0:2024.1-1.fc41.no 100% | 3.9 MiB/s | 60.5 KiB | 00m00s [ 6/24] python3-asgiref-0:3.7.2-3.fc41. 100% | 5.1 MiB/s | 57.9 KiB | 00m00s [ 7/24] python3-sqlparse-0:0.4.2-9.fc41 100% | 6.5 MiB/s | 106.1 KiB | 00m00s [ 8/24] python3-jwt+crypto-0:2.6.0-6.fc 100% | 618.6 KiB/s | 9.3 KiB | 00m00s [ 9/24] python3-openid-0:3.1.0-21.fc41. 100% | 19.0 MiB/s | 252.7 KiB | 00m00s [10/24] python3-jwt-0:2.6.0-6.fc41.noar 100% | 3.1 MiB/s | 54.5 KiB | 00m00s [11/24] python3-requests-0:2.31.0-4.fc4 100% | 46.8 MiB/s | 143.8 KiB | 00m00s [12/24] python3-pytest-0:7.4.3-3.fc41.n 100% | 175.2 MiB/s | 717.5 KiB | 00m00s [13/24] python3-cryptography-0:42.0.5-1 100% | 121.0 MiB/s | 1.2 MiB | 00m00s [14/24] python3-requests-oauthlib-0:1.3 100% | 2.4 MiB/s | 48.9 KiB | 00m00s [15/24] python3-charset-normalizer-0:3. 100% | 48.8 MiB/s | 100.0 KiB | 00m00s [16/24] python3-idna-0:3.7-1.fc41.noarc 100% | 21.7 MiB/s | 110.9 KiB | 00m00s [17/24] python3-defusedxml-0:0.7.1-13.f 100% | 3.6 MiB/s | 52.3 KiB | 00m00s [18/24] python3-urllib3-0:1.26.18-4.fc4 100% | 63.2 MiB/s | 259.1 KiB | 00m00s [19/24] python3-iniconfig-0:1.1.1-20.fc 100% | 18.1 MiB/s | 18.5 KiB | 00m00s [20/24] python3-cffi-0:1.16.0-4.fc41.x8 100% | 72.5 MiB/s | 296.8 KiB | 00m00s [21/24] python3-pycparser-0:2.20-16.fc4 100% | 36.4 MiB/s | 149.0 KiB | 00m00s [22/24] python3-ply-0:3.11-23.fc41.noar 100% | 43.1 MiB/s | 132.5 KiB | 00m00s [23/24] python3-oauthlib-0:3.2.2-1.fc40 100% | 11.2 MiB/s | 218.8 KiB | 00m00s [24/24] python3-django-0:4.2.11-3.fc41. 100% | 32.9 MiB/s | 5.0 MiB | 00m00s -------------------------------------------------------------------------------- [24/24] Total 100% | 67.2 MiB/s | 10.3 MiB | 00m00s Running transaction [ 1/26] Verify package files 100% | 558.0 B/s | 24.0 B | 00m00s [ 2/26] Prepare transaction 100% | 413.0 B/s | 24.0 B | 00m00s [ 3/26] Installing python3-idna-0:3.7-1 100% | 196.0 MiB/s | 602.0 KiB | 00m00s [ 4/26] Installing python3-urllib3-0:1. 100% | 200.2 MiB/s | 1.0 MiB | 00m00s [ 5/26] Installing python3-ply-0:3.11-2 100% | 280.5 MiB/s | 574.5 KiB | 00m00s [ 6/26] Installing python3-pycparser-0: 100% | 270.9 MiB/s | 832.2 KiB | 00m00s [ 7/26] Installing python3-cffi-0:1.16. 100% | 265.8 MiB/s | 1.3 MiB | 00m00s [ 8/26] Installing python3-cryptography 100% | 243.2 MiB/s | 4.6 MiB | 00m00s [ 9/26] Installing python3-jwt-0:2.6.0- 100% | 147.7 MiB/s | 151.2 KiB | 00m00s [10/26] Installing python3-jwt+crypto-0 100% | 0.0 B/s | 124.0 B | 00m00s [11/26] Installing python3-iniconfig-0: 100% | 23.0 MiB/s | 23.5 KiB | 00m00s [12/26] Installing python3-pytest-0:7.4 100% | 328.4 MiB/s | 3.6 MiB | 00m00s [13/26] Installing python3-oauthlib-0:3 100% | 144.8 MiB/s | 1.0 MiB | 00m00s [14/26] Installing python3-charset-norm 100% | 158.6 MiB/s | 324.7 KiB | 00m00s [15/26] Installing python3-requests-0:2 100% | 231.5 MiB/s | 474.1 KiB | 00m00s [16/26] Installing python3-requests-oau 100% | 71.2 MiB/s | 145.8 KiB | 00m00s [17/26] Installing python3-defusedxml-0 100% | 100.7 MiB/s | 206.3 KiB | 00m00s [18/26] Installing python3-openid-0:3.1 100% | 225.0 MiB/s | 1.1 MiB | 00m00s [19/26] Installing python3-sqlparse-0:0 100% | 182.8 MiB/s | 374.4 KiB | 00m00s [20/26] Installing python3-asgiref-0:3. 100% | 19.9 MiB/s | 183.7 KiB | 00m00s [21/26] Installing python3-django-0:4.2 100% | 81.1 MiB/s | 21.7 MiB | 00m00s [22/26] Installing python3-django-allau 100% | 91.0 MiB/s | 5.7 MiB | 00m00s [23/26] Installing python3-mailmanclien 100% | 199.4 MiB/s | 1.0 MiB | 00m00s [24/26] Installing python3-pytest-djang 100% | 148.4 MiB/s | 151.9 KiB | 00m00s [25/26] Installing python3-pytz-0:2024. 100% | 223.4 MiB/s | 228.7 KiB | 00m00s [26/26] Installing python3-django-grava 100% | 854.4 KiB/s | 42.7 KiB | 00m00s >>> Running trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 >>> Stop trigger-install scriptlet: glibc-common-0:2.39.9000-14.fc41.x86_64 Warning: skipped PGP checks for 24 package(s). Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.NWOKuk + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + RPM_TOXENV=py313 + 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.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.1.1) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.43.0) 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.43.0) 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) py313: OK (0.00 seconds) congratulations :) (0.04 seconds) Handling tox from tox --print-deps-only: py313 Requirement satisfied: tox (installed: tox 4.14.2) Handling mailmanclient from tox --print-deps-only: py313 Requirement satisfied: mailmanclient (installed: mailmanclient 3.3.3) Handling pytest-django from tox --print-deps-only: py313 Requirement satisfied: pytest-django (installed: pytest-django 4.8.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.11/django_mailman3-1.3.11.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.11) 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 >=0.56 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django-allauth >=0.56 (installed: django-allauth 0.61.1) 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 2024.1) + cat /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires + rm -rfv django_mailman3-1.3.11.dist-info/ removed 'django_mailman3-1.3.11.dist-info/COPYING.txt' removed 'django_mailman3-1.3.11.dist-info/METADATA' removed 'django_mailman3-1.3.11.dist-info/top_level.txt' removed directory 'django_mailman3-1.3.11.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.buildreqs.nosrc.rpm INFO: Going to install missing dynamic buildrequires Updating and loading repositories: Additional repo http_kojipkgs_fedorapr 100% | 69.9 KiB/s | 4.1 KiB | 00m00s fedora 100% | 223.8 KiB/s | 19.9 KiB | 00m00s Copr repository 100% | 96.1 KiB/s | 1.5 KiB | 00m00s Repositories loaded. Nothing to do. Package "pyproject-rpm-macros-1.12.0-1.fc40.noarch" is already installed. Package "python3-devel-3.13.0~a6-2.1.fc41.x86_64" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "python3-django-allauth-0.61.1-1.fc41.noarch" is already installed. Package "python3-django-gravatar2-1.4.4-9.fc41.noarch" is already installed. Package "python3-mailmanclient-3.3.3-10.fc41.noarch" is already installed. Package "python3-mailmanclient-3.3.3-10.fc41.noarch" is already installed. Package "python3-packaging-24.0-1.fc41.noarch" is already installed. Package "python3-pip-24.0-2.fc41.noarch" is already installed. Package "python3-pytest-django-4.8.0-1.fc41.noarch" is already installed. Package "python3-pytz-2024.1-1.fc41.noarch" is already installed. Package "python3-setuptools-69.1.1-2.fc41~bootstrap.noarch" is already installed. Package "tox-4.14.2-1.fc41.noarch" is already installed. Package "python3-tox-current-env-0.0.11-9.fc41.noarch" is already installed. Package "python3-wheel-1:0.43.0-1.fc41.noarch" is already installed. Building target platforms: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1714003200 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.7URLXE + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + RPM_TOXENV=py313 + 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.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.1.1) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.43.0) 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.43.0) 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) py313: OK (0.00 seconds) congratulations :) (0.04 seconds) Handling tox from tox --print-deps-only: py313 Requirement satisfied: tox (installed: tox 4.14.2) Handling mailmanclient from tox --print-deps-only: py313 Requirement satisfied: mailmanclient (installed: mailmanclient 3.3.3) Handling pytest-django from tox --print-deps-only: py313 Requirement satisfied: pytest-django (installed: pytest-django 4.8.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.11/django_mailman3-1.3.11.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.11) 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 >=0.56 from hook generated metadata: Requires-Dist (django-mailman3) Requirement satisfied: django-allauth >=0.56 (installed: django-allauth 0.61.1) 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 2024.1) + cat /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-buildrequires + rm -rfv django_mailman3-1.3.11.dist-info/ removed 'django_mailman3-1.3.11.dist-info/COPYING.txt' removed 'django_mailman3-1.3.11.dist-info/METADATA' removed 'django_mailman3-1.3.11.dist-info/top_level.txt' removed directory 'django_mailman3-1.3.11.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.25cPQF + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11 + mkdir -p /builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/django-mailman3-1.3.11/pyproject-wheeldir Processing /builddir/build/BUILD/django-mailman3-1.3.11 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) running dist_info creating /builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info writing /builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info/PKG-INFO writing dependency_links to /builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info/dependency_links.txt writing requirements to /builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info/requires.txt writing top-level names to /builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info/top_level.txt writing manifest file '/builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info/SOURCES.txt' reading manifest file '/builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/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.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-b2490a0_/django_mailman3-1.3.11.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_lib_auth_fedora_provider.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_forms.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_delete_account.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/0003_sessions.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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_mailman3.locale.ak.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_mailman3.locale.ak.LC_MESSAGES' as an importable package[^1], but it is 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.ak.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read 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.ak.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_mailman3.locale.ak.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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.13/site-packages/setuptools/command/build_py.py:207: _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/ak creating build/lib/django_mailman3/locale/ak/LC_MESSAGES copying django_mailman3/locale/ak/LC_MESSAGES/django.po -> build/lib/django_mailman3/locale/ak/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/ak creating build/bdist.linux-x86_64/wheel/django_mailman3/locale/ak/LC_MESSAGES copying build/lib/django_mailman3/locale/ak/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django_mailman3/locale/ak/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/0003_sessions.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_delete_account.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_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_lib_auth_fedora_provider.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.11-py3.13.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/django_mailman3-1.3.11.dist-info/WHEEL creating '/builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir/pip-wheel-f2kdswp4/.tmp-7zrewe7d/django_mailman3-1.3.11-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/ak/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/0003_sessions.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.11.dist-info/COPYING.txt' adding 'django_mailman3-1.3.11.dist-info/METADATA' adding 'django_mailman3-1.3.11.dist-info/WHEEL' adding 'django_mailman3-1.3.11.dist-info/top_level.txt' adding 'django_mailman3-1.3.11.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.11-py3-none-any.whl size=721953 sha256=cc56812fc133d2372fa869c3a918a9cb18bdec8fe87d4047d8aba9e0a4c0e798 Stored in directory: /builddir/.cache/pip/wheels/03/e6/d7/317129a98a7c7eb5145cd155cb4bd669ab7afac580a01a0e07 Successfully built django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.QiiDfG + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 ++ dirname /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11 ++ ls /builddir/build/BUILD/django-mailman3-1.3.11/pyproject-wheeldir/django_mailman3-1.3.11-py3-none-any.whl ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' ++ xargs basename --multiple + specifier=django_mailman3==1.3.11 + '[' -z django_mailman3==1.3.11 ']' + TMPDIR=/builddir/build/BUILD/django-mailman3-1.3.11/.pyproject-builddir + /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.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.11/pyproject-wheeldir django_mailman3==1.3.11 Using pip 24.0 from /usr/lib/python3.13/site-packages/pip (python 3.13) Looking in links: /builddir/build/BUILD/django-mailman3-1.3.11/pyproject-wheeldir Processing ./pyproject-wheeldir/django_mailman3-1.3.11-py3-none-any.whl Installing collected packages: django_mailman3 Successfully installed django_mailman3-1.3.11 + '[' -d /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/bin ']' + rm -f /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-ghost-distinfo + site_dirs=() + '[' -d /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages ']' + site_dirs+=("/usr/lib/python3.13/site-packages") + '[' /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib64/python3.13/site-packages '!=' /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages ']' + '[' -d /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib64/python3.13/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info' + sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.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.11-2.fc41.x86_64 --record /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/RECORD --output /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-record + rm -fv /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/RECORD removed '/builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/RECORD' + rm -fv /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/REQUESTED removed '/builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/REQUESTED' ++ wc -l /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.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.11-2.fc41.x86_64-pyproject-files --output-modules /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-modules --buildroot /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 --sitelib /usr/lib/python3.13/site-packages --sitearch /usr/lib64/python3.13/site-packages --python-version 3.13 --pyproject-record /builddir/build/BUILD/python-django-mailman3-1.3.11-2.fc41.x86_64-pyproject-record --prefix /usr django_mailman3 + /usr/bin/find-debuginfo -j4 --strict-build-id -m -i --build-id-seed 1.3.11-2.fc41 --unique-debug-suffix -1.3.11-2.fc41.x86_64 --unique-debug-src-base python-django-mailman3-1.3.11-2.fc41.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.11 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.11-2.fc41.x86_64/usr/lib/python3.13 using python3.13 + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.Rr5cdA + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11 + PYTHONPATH=.: + TOX_TESTENV_PASSENV='*' + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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.11-2.fc41.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.11/.pyproject-builddir' + PYTEST_XDIST_AUTO_NUM_WORKERS=4 + HOSTNAME=rpmbuild + /usr/bin/python3 -m tox --current-env -q --recreate -e py313 ============================= test session starts ============================== platform linux -- Python 3.13.0a6, pytest-7.4.3, pluggy-1.3.0 cachedir: .tox/py313/.pytest_cache django: version: 4.2.11, settings: django_mailman3.tests.settings_test (from option) rootdir: /builddir/build/BUILD/django-mailman3-1.3.11 configfile: pytest.ini plugins: django-4.8.0 collected 84 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 ............s...... 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.13/site-packages/django/conf/__init__.py:267 /usr/lib/python3.13/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.13/site-packages/openid/oidutil.py:106 /usr/lib/python3.13/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.11/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 ================== 83 passed, 1 skipped, 3 warnings in 7.55s =================== py313: OK (8.01 seconds) congratulations :) (8.05 seconds) + RPM_EC=0 ++ jobs -p + exit 0 Processing files: python3-django-mailman3-1.3.11-2.fc41.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.81UX4k + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + DOCDIR=/builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.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.11-2.fc41.x86_64/usr/share/doc/python3-django-mailman3 + cp -pr /builddir/build/BUILD/django-mailman3-1.3.11/README.rst /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/share/doc/python3-django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.djFOS4 + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + LICENSEDIR=/builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.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.11-2.fc41.x86_64/usr/share/licenses/python3-django-mailman3 + cp -pr /builddir/build/BUILD/django-mailman3-1.3.11/COPYING.txt /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64/usr/share/licenses/python3-django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-mailman3 = 1.3.11-2.fc41 python3-django-mailman3 = 1.3.11-2.fc41 python3.13-django-mailman3 = 1.3.11-2.fc41 python3.13dist(django-mailman3) = 1.3.11 python3dist(django-mailman3) = 1.3.11 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: (python3.13dist(django) < 4.3~~ with python3.13dist(django) >= 3.2) python(abi) = 3.13 python3.13dist(django-allauth) >= 0.56 python3.13dist(django-gravatar2) >= 1.0.6 python3.13dist(mailmanclient) >= 3.3.3 python3.13dist(pytz) Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-2.fc41.src.rpm Wrote: /builddir/build/RPMS/python3-django-mailman3-1.3.11-2.fc41.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.iQNfnn + umask 022 + cd /builddir/build/BUILD + cd django-mailman3-1.3.11 + /usr/bin/rm -rf /builddir/build/BUILDROOT/python-django-mailman3-1.3.11-2.fc41.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.BEHau1 + umask 022 + cd /builddir/build/BUILD + rm -rf /builddir/build/BUILD/django-mailman3-1.3.11-SPECPARTS + rm -rf django-mailman3-1.3.11 django-mailman3-1.3.11.gemspec + RPM_EC=0 ++ jobs -p + exit 0 Finish: rpmbuild python-django-mailman3-1.3.11-2.fc41.src.rpm Finish: build phase for python-django-mailman3-1.3.11-2.fc41.src.rpm INFO: chroot_scan: 1 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/fedora-rawhide-x86_64-1714048811.076583/root/var/log/dnf5.log INFO: Done(/var/lib/copr-rpmbuild/results/python-django-mailman3-1.3.11-2.fc41.src.rpm) Config(child) 0 minutes 23 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.11", "release": "2.fc41", "arch": "src" }, { "name": "python3-django-mailman3", "epoch": null, "version": "1.3.11", "release": "2.fc41", "arch": "noarch" } ] } RPMResults finished