Mock Version: 5.6 Mock Version: 5.6 Mock Version: 5.6 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'], chrootPath='/var/lib/mock/f41-build-51705011-6189392/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '84b705463e07432b85a2b3660a3e0981', '-D', '/var/lib/mock/f41-build-51705011-6189392/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1709164800 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-1.fc41.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'], chrootPath='/var/lib/mock/f41-build-51705011-6189392/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueraiseExc=FalseprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '79c2a1c4c47e46c2b336be88537670ce', '-D', '/var/lib/mock/f41-build-51705011-6189392/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1709164800 Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.czT8Sv + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-build + test -d /builddir/build/BUILD/python-django-mailman3-1.3.11-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /builddir/build/BUILD/python-django-mailman3-1.3.11-build + /usr/bin/rm -rf /builddir/build/BUILD/python-django-mailman3-1.3.11-build + /usr/bin/mkdir -p /builddir/build/BUILD/python-django-mailman3-1.3.11-build + /usr/bin/mkdir -p /builddir/build/BUILD/python-django-mailman3-1.3.11-build/SPECPARTS + RPM_EC=0 ++ jobs -p + exit 0 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.uvZyAM + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-build + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 + /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 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.tZmbqw + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + 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/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.2.0) 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-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-1.fc41.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'], chrootPath='/var/lib/mock/f41-build-51705011-6189392/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueraiseExc=FalseprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'da38eb523be9444b85efc87a36652bae', '-D', '/var/lib/mock/f41-build-51705011-6189392/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1709164800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.urkqzC + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + 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/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.2.0) 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-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-1.fc41.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'], chrootPath='/var/lib/mock/f41-build-51705011-6189392/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueraiseExc=FalseprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '326119f9ea374c95af6d8d869ffaa210', '-D', '/var/lib/mock/f41-build-51705011-6189392/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1709164800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.ByHmRT + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + 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/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.2.0) 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.01 seconds) congratulations :) (0.13 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/python-django-mailman3-1.3.11-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-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires + rm -rfv django_mailman3-1.3.11.dist-info/ removed 'django_mailman3-1.3.11.dist-info/top_level.txt' removed 'django_mailman3-1.3.11.dist-info/METADATA' removed 'django_mailman3-1.3.11.dist-info/COPYING.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-1.fc41.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'], chrootPath='/var/lib/mock/f41-build-51705011-6189392/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueraiseExc=FalseprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '0ea1db9e9455427da956d9978f052efe', '-D', '/var/lib/mock/f41-build-51705011-6189392/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-mailman3.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1709164800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.K9T1It + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + 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/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.2.0) 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.01 seconds) congratulations :) (0.09 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/python-django-mailman3-1.3.11-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-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires + rm -rfv django_mailman3-1.3.11.dist-info/ removed 'django_mailman3-1.3.11.dist-info/top_level.txt' removed 'django_mailman3-1.3.11.dist-info/METADATA' removed 'django_mailman3-1.3.11.dist-info/COPYING.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-1.fc41.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch /builddir/build/SPECS/python-django-mailman3.spec'], chrootPath='/var/lib/mock/f41-build-51705011-6189392/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '84f5e07cebe3408a88d10c31c95cf33d', '-D', '/var/lib/mock/f41-build-51705011-6189392/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.kwhy4up4:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch /builddir/build/SPECS/python-django-mailman3.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1709164800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.e1eMJy + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + 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/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir --output /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires -t Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 69.2.0) 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.01 seconds) congratulations :) (0.10 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/python-django-mailman3-1.3.11-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-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-buildrequires + rm -rfv django_mailman3-1.3.11.dist-info/ removed 'django_mailman3-1.3.11.dist-info/top_level.txt' removed 'django_mailman3-1.3.11.dist-info/METADATA' removed 'django_mailman3-1.3.11.dist-info/COPYING.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.VGydWo + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-mailman3-1.3.11 + mkdir -p /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir Processing /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) running dist_info creating /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info writing /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info/PKG-INFO writing dependency_links to /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info/dependency_links.txt writing requirements to /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info/requires.txt writing top-level names to /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info/top_level.txt writing manifest file '/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info/SOURCES.txt' reading manifest file '/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/django_mailman3.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-modern-metadata-4ry008b0/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/__init__.py -> build/lib/django_mailman3 copying django_mailman3/admin.py -> build/lib/django_mailman3 copying django_mailman3/apps.py -> build/lib/django_mailman3 copying django_mailman3/context_processors.py -> build/lib/django_mailman3 copying django_mailman3/forms.py -> build/lib/django_mailman3 copying django_mailman3/models.py -> build/lib/django_mailman3 copying django_mailman3/signals.py -> build/lib/django_mailman3 copying django_mailman3/urls.py -> build/lib/django_mailman3 creating build/lib/django_mailman3/lib copying django_mailman3/lib/__init__.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/mailman.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/paginator.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/scrub.py -> build/lib/django_mailman3/lib copying django_mailman3/lib/user.py -> build/lib/django_mailman3/lib creating build/lib/django_mailman3/middleware copying django_mailman3/middleware/__init__.py -> build/lib/django_mailman3/middleware creating build/lib/django_mailman3/migrations copying django_mailman3/migrations/0001_initial.py -> build/lib/django_mailman3/migrations copying django_mailman3/migrations/0002_maildomain.py -> build/lib/django_mailman3/migrations copying django_mailman3/migrations/0003_sessions.py -> build/lib/django_mailman3/migrations copying django_mailman3/migrations/__init__.py -> build/lib/django_mailman3/migrations creating build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/__init__.py -> build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/bootstrap_tags.py -> build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/d_gravatar.py -> build/lib/django_mailman3/templatetags copying django_mailman3/templatetags/pagination.py -> build/lib/django_mailman3/templatetags creating build/lib/django_mailman3/tests copying django_mailman3/tests/__init__.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/settings_test.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_bootstrap_tags.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_context_processors.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_delete_account.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_forms.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_lib_auth_fedora_provider.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_lib_user.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_mailman.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_middlewares.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_paginator.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_scrub.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_signals.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/test_view_profile.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/urls_test.py -> build/lib/django_mailman3/tests copying django_mailman3/tests/utils.py -> build/lib/django_mailman3/tests creating build/lib/django_mailman3/views copying django_mailman3/views/__init__.py -> build/lib/django_mailman3/views copying django_mailman3/views/profile.py -> build/lib/django_mailman3/views copying django_mailman3/views/user_adapter.py -> build/lib/django_mailman3/views 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/__init__.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/urls.py -> build/lib/django_mailman3/lib/auth/fedora copying django_mailman3/lib/auth/fedora/views.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-ppc64le/wheel running install running install_lib creating build/bdist.linux-ppc64le creating build/bdist.linux-ppc64le/wheel creating build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/admin.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/apps.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/context_processors.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/forms.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/models.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/signals.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 copying build/lib/django_mailman3/urls.py -> build/bdist.linux-ppc64le/wheel/django_mailman3 creating build/bdist.linux-ppc64le/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/mailman.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/paginator.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/scrub.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib copying build/lib/django_mailman3/lib/user.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib creating build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth copying build/lib/django_mailman3/lib/auth/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth creating build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/provider.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/urls.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth/fedora copying build/lib/django_mailman3/lib/auth/fedora/views.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/lib/auth/fedora creating build/bdist.linux-ppc64le/wheel/django_mailman3/middleware copying build/lib/django_mailman3/middleware/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/middleware creating build/bdist.linux-ppc64le/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/0001_initial.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/0002_maildomain.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/0003_sessions.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/migrations copying build/lib/django_mailman3/migrations/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/migrations creating build/bdist.linux-ppc64le/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/bootstrap_tags.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/d_gravatar.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/templatetags copying build/lib/django_mailman3/templatetags/pagination.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/templatetags creating build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/settings_test.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_bootstrap_tags.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_context_processors.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_delete_account.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_forms.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_lib_auth_fedora_provider.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_lib_user.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_mailman.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_middlewares.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_paginator.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_scrub.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_signals.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/test_view_profile.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/urls_test.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests copying build/lib/django_mailman3/tests/utils.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests creating build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attached_message.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-1.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-2.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-3.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-4.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/attachment-5.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/bad_charset.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/email-bad-filename.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/html-email-1.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/html-email-2.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/null_byte.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/null_byte_multipart.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/payload-iso8859.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/payload-unknown.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/payload-utf8.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata copying build/lib/django_mailman3/tests/testdata/pipermail_nextpart.txt -> build/bdist.linux-ppc64le/wheel/django_mailman3/tests/testdata creating build/bdist.linux-ppc64le/wheel/django_mailman3/views copying build/lib/django_mailman3/views/__init__.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/views copying build/lib/django_mailman3/views/profile.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/views copying build/lib/django_mailman3/views/user_adapter.py -> build/bdist.linux-ppc64le/wheel/django_mailman3/views creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/af creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/af/LC_MESSAGES copying build/lib/django_mailman3/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/af/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ak creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ak/LC_MESSAGES copying build/lib/django_mailman3/locale/ak/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ak/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/am creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/am/LC_MESSAGES copying build/lib/django_mailman3/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/am/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/an creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/an/LC_MESSAGES copying build/lib/django_mailman3/locale/an/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/an/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ar creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ar/LC_MESSAGES copying build/lib/django_mailman3/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ar/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ast creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ast/LC_MESSAGES copying build/lib/django_mailman3/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ast/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/az creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/az/LC_MESSAGES copying build/lib/django_mailman3/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/az/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/be creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/be/LC_MESSAGES copying build/lib/django_mailman3/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/be/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bem creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bem/LC_MESSAGES copying build/lib/django_mailman3/locale/bem/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bem/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bg creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bg/LC_MESSAGES copying build/lib/django_mailman3/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bg/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bn creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bn/LC_MESSAGES copying build/lib/django_mailman3/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bn/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bo creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bo/LC_MESSAGES copying build/lib/django_mailman3/locale/bo/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bo/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/br creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/br/LC_MESSAGES copying build/lib/django_mailman3/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/br/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bs creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bs/LC_MESSAGES copying build/lib/django_mailman3/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/bs/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ca creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ca/LC_MESSAGES copying build/lib/django_mailman3/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ca/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ca@valencia creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ca@valencia/LC_MESSAGES copying build/lib/django_mailman3/locale/ca@valencia/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ca@valencia/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ce creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ce/LC_MESSAGES copying build/lib/django_mailman3/locale/ce/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ce/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ckb creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ckb/LC_MESSAGES copying build/lib/django_mailman3/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ckb/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/co creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/co/LC_MESSAGES copying build/lib/django_mailman3/locale/co/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/co/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/crh creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/crh/LC_MESSAGES copying build/lib/django_mailman3/locale/crh/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/crh/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cs creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cs/LC_MESSAGES copying build/lib/django_mailman3/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cs/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cv creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cv/LC_MESSAGES copying build/lib/django_mailman3/locale/cv/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cv/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cy creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cy/LC_MESSAGES copying build/lib/django_mailman3/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/cy/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/da creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/da/LC_MESSAGES copying build/lib/django_mailman3/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/da/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/de creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/de/LC_MESSAGES copying build/lib/django_mailman3/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/de/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/el creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/el/LC_MESSAGES copying build/lib/django_mailman3/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/el/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_AU creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_AU/LC_MESSAGES copying build/lib/django_mailman3/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_AU/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_CA creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_CA/LC_MESSAGES copying build/lib/django_mailman3/locale/en_CA/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_CA/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_GB creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_GB/LC_MESSAGES copying build/lib/django_mailman3/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/en_GB/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/eo creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/eo/LC_MESSAGES copying build/lib/django_mailman3/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/eo/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/es creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/es/LC_MESSAGES copying build/lib/django_mailman3/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/es/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/et creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/et/LC_MESSAGES copying build/lib/django_mailman3/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/et/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/eu creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/eu/LC_MESSAGES copying build/lib/django_mailman3/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/eu/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fa creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fa/LC_MESSAGES copying build/lib/django_mailman3/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fa/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fi creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fi/LC_MESSAGES copying build/lib/django_mailman3/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fi/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fil creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fil/LC_MESSAGES copying build/lib/django_mailman3/locale/fil/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fil/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fo creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fo/LC_MESSAGES copying build/lib/django_mailman3/locale/fo/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fo/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fr creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fr/LC_MESSAGES copying build/lib/django_mailman3/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fr/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fr_CA creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fr_CA/LC_MESSAGES copying build/lib/django_mailman3/locale/fr_CA/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fr_CA/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/frp creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/frp/LC_MESSAGES copying build/lib/django_mailman3/locale/frp/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/frp/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fy creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fy/LC_MESSAGES copying build/lib/django_mailman3/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/fy/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ga creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ga/LC_MESSAGES copying build/lib/django_mailman3/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ga/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gd creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gd/LC_MESSAGES copying build/lib/django_mailman3/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gd/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gl creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gl/LC_MESSAGES copying build/lib/django_mailman3/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gl/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gu creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gu/LC_MESSAGES copying build/lib/django_mailman3/locale/gu/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/gu/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/he creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/he/LC_MESSAGES copying build/lib/django_mailman3/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/he/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hi creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hi/LC_MESSAGES copying build/lib/django_mailman3/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hi/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hr creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hr/LC_MESSAGES copying build/lib/django_mailman3/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hr/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ht creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ht/LC_MESSAGES copying build/lib/django_mailman3/locale/ht/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ht/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hu creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hu/LC_MESSAGES copying build/lib/django_mailman3/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hu/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hy creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hy/LC_MESSAGES copying build/lib/django_mailman3/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/hy/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ia creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ia/LC_MESSAGES copying build/lib/django_mailman3/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ia/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/id creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/id/LC_MESSAGES copying build/lib/django_mailman3/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/id/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/is creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/is/LC_MESSAGES copying build/lib/django_mailman3/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/is/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/it creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/it/LC_MESSAGES copying build/lib/django_mailman3/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/it/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ja creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ja/LC_MESSAGES copying build/lib/django_mailman3/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ja/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ka creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ka/LC_MESSAGES copying build/lib/django_mailman3/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ka/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kk creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kk/LC_MESSAGES copying build/lib/django_mailman3/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kk/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kl creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kl/LC_MESSAGES copying build/lib/django_mailman3/locale/kl/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kl/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/km creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/km/LC_MESSAGES copying build/lib/django_mailman3/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/km/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kn creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kn/LC_MESSAGES copying build/lib/django_mailman3/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kn/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ko creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ko/LC_MESSAGES copying build/lib/django_mailman3/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ko/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ku creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ku/LC_MESSAGES copying build/lib/django_mailman3/locale/ku/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ku/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kw creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kw/LC_MESSAGES copying build/lib/django_mailman3/locale/kw/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/kw/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ky creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ky/LC_MESSAGES copying build/lib/django_mailman3/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ky/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/la creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/la/LC_MESSAGES copying build/lib/django_mailman3/locale/la/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/la/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lb creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lb/LC_MESSAGES copying build/lib/django_mailman3/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lb/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lo creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lo/LC_MESSAGES copying build/lib/django_mailman3/locale/lo/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lo/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lt creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lt/LC_MESSAGES copying build/lib/django_mailman3/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lt/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lv creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lv/LC_MESSAGES copying build/lib/django_mailman3/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/lv/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mg creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mg/LC_MESSAGES copying build/lib/django_mailman3/locale/mg/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mg/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mhr creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mhr/LC_MESSAGES copying build/lib/django_mailman3/locale/mhr/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mhr/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mi creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mi/LC_MESSAGES copying build/lib/django_mailman3/locale/mi/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mi/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ml creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ml/LC_MESSAGES copying build/lib/django_mailman3/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ml/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mr creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mr/LC_MESSAGES copying build/lib/django_mailman3/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/mr/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ms creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ms/LC_MESSAGES copying build/lib/django_mailman3/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ms/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/my creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/my/LC_MESSAGES copying build/lib/django_mailman3/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/my/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nb_NO creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nb_NO/LC_MESSAGES copying build/lib/django_mailman3/locale/nb_NO/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nb_NO/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ne creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ne/LC_MESSAGES copying build/lib/django_mailman3/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ne/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nl creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nl/LC_MESSAGES copying build/lib/django_mailman3/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nl/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nn_NO creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nn_NO/LC_MESSAGES copying build/lib/django_mailman3/locale/nn_NO/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/nn_NO/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/oc creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/oc/LC_MESSAGES copying build/lib/django_mailman3/locale/oc/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/oc/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/os creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/os/LC_MESSAGES copying build/lib/django_mailman3/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/os/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pa creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pa/LC_MESSAGES copying build/lib/django_mailman3/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pa/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pl creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pl/LC_MESSAGES copying build/lib/django_mailman3/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pl/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ps creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ps/LC_MESSAGES copying build/lib/django_mailman3/locale/ps/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ps/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pt creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pt/LC_MESSAGES copying build/lib/django_mailman3/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pt/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pt_BR creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pt_BR/LC_MESSAGES copying build/lib/django_mailman3/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ro creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ro/LC_MESSAGES copying build/lib/django_mailman3/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ro/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ru creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ru/LC_MESSAGES copying build/lib/django_mailman3/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ru/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sa creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sa/LC_MESSAGES copying build/lib/django_mailman3/locale/sa/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sa/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sc creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sc/LC_MESSAGES copying build/lib/django_mailman3/locale/sc/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sc/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sd creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sd/LC_MESSAGES copying build/lib/django_mailman3/locale/sd/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sd/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/se creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/se/LC_MESSAGES copying build/lib/django_mailman3/locale/se/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/se/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/shn creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/shn/LC_MESSAGES copying build/lib/django_mailman3/locale/shn/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/shn/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/si creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/si/LC_MESSAGES copying build/lib/django_mailman3/locale/si/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/si/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sk creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sk/LC_MESSAGES copying build/lib/django_mailman3/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sk/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sl creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sl/LC_MESSAGES copying build/lib/django_mailman3/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sl/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sq creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sq/LC_MESSAGES copying build/lib/django_mailman3/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sq/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sr creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sr/LC_MESSAGES copying build/lib/django_mailman3/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sr/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sv creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sv/LC_MESSAGES copying build/lib/django_mailman3/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sv/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sw creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sw/LC_MESSAGES copying build/lib/django_mailman3/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/sw/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/szl creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/szl/LC_MESSAGES copying build/lib/django_mailman3/locale/szl/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/szl/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ta creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ta/LC_MESSAGES copying build/lib/django_mailman3/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ta/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/te creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/te/LC_MESSAGES copying build/lib/django_mailman3/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/te/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/tg creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/tg/LC_MESSAGES copying build/lib/django_mailman3/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/tg/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/th creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/th/LC_MESSAGES copying build/lib/django_mailman3/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/th/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ti creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ti/LC_MESSAGES copying build/lib/django_mailman3/locale/ti/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ti/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/tr creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/tr/LC_MESSAGES copying build/lib/django_mailman3/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/tr/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ug creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ug/LC_MESSAGES copying build/lib/django_mailman3/locale/ug/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ug/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/uk creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/uk/LC_MESSAGES copying build/lib/django_mailman3/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/uk/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ur creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ur/LC_MESSAGES copying build/lib/django_mailman3/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/ur/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/uz creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/uz/LC_MESSAGES copying build/lib/django_mailman3/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/uz/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/vi creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/vi/LC_MESSAGES copying build/lib/django_mailman3/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/vi/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/wae creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/wae/LC_MESSAGES copying build/lib/django_mailman3/locale/wae/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/wae/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_CN creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_CN/LC_MESSAGES copying build/lib/django_mailman3/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_CN/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_HK creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_HK/LC_MESSAGES copying build/lib/django_mailman3/locale/zh_HK/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_HK/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_TW creating build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_TW/LC_MESSAGES copying build/lib/django_mailman3/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.linux-ppc64le/wheel/django_mailman3/locale/zh_TW/LC_MESSAGES creating build/bdist.linux-ppc64le/wheel/django_mailman3/static creating build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3 creating build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/css copying build/lib/django_mailman3/static/django-mailman3/css/main.css -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/css creating build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img creating build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/facebook.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/fedora.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/github.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/gitlab.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/google.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/openid.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/stackexchange.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/stackoverflow.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/twitter.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login copying build/lib/django_mailman3/static/django-mailman3/img/login/yahoo.png -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/img/login creating build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/js copying build/lib/django_mailman3/static/django-mailman3/js/main.js -> build/bdist.linux-ppc64le/wheel/django_mailman3/static/django-mailman3/js creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/email.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/email_confirm.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/login.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/logout.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_change.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_reset.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_reset_from_key.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/password_set.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account copying build/lib/django_mailman3/templates/account/signup.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/account creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3 copying build/lib/django_mailman3/templates/django_mailman3/base.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3 copying build/lib/django_mailman3/templates/django_mailman3/login_extra_post_providers.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3 copying build/lib/django_mailman3/templates/django_mailman3/login_extra_top.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3 creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/bootstrap copying build/lib/django_mailman3/templates/django_mailman3/bootstrap/form-horizontal.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/bootstrap copying build/lib/django_mailman3/templates/django_mailman3/bootstrap/form.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/bootstrap creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/paginator copying build/lib/django_mailman3/templates/django_mailman3/paginator/pagination.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/paginator creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/profile copying build/lib/django_mailman3/templates/django_mailman3/profile/base.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/profile copying build/lib/django_mailman3/templates/django_mailman3/profile/delete_profile.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/profile copying build/lib/django_mailman3/templates/django_mailman3/profile/profile.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/django_mailman3/profile creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/openid copying build/lib/django_mailman3/templates/openid/login.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/openid creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/socialaccount copying build/lib/django_mailman3/templates/socialaccount/connections.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/socialaccount copying build/lib/django_mailman3/templates/socialaccount/signup.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/socialaccount creating build/bdist.linux-ppc64le/wheel/django_mailman3/templates/socialaccount/snippets copying build/lib/django_mailman3/templates/socialaccount/snippets/provider_list.html -> build/bdist.linux-ppc64le/wheel/django_mailman3/templates/socialaccount/snippets running install_egg_info Copying django_mailman3.egg-info to build/bdist.linux-ppc64le/wheel/django_mailman3-1.3.11-py3.13.egg-info running install_scripts creating build/bdist.linux-ppc64le/wheel/django_mailman3-1.3.11.dist-info/WHEEL creating '/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir/pip-wheel-bs7145t8/.tmp-n_i783ch/django_mailman3-1.3.11-py3-none-any.whl' and adding 'build/bdist.linux-ppc64le/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-ppc64le/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=722492 sha256=c99289de5ad0b28413e7887d5b3a7c1d0701aab61bc514671652f5b844fe9be8 Stored in directory: /builddir/.cache/pip/wheels/48/15/80/092c445868abdc0c3f81a96e0f4107e183e2e9001ea0b6a71e Successfully built django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.n71tLY + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-build + '[' /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT '!=' / ']' + rm -rf /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT ++ dirname /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT + mkdir -p /builddir/build/BUILD/python-django-mailman3-1.3.11-build + mkdir /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-mailman3-1.3.11 ++ ls /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/pyproject-wheeldir/django_mailman3-1.3.11-py3-none-any.whl ++ xargs basename --multiple ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=django_mailman3==1.3.11 + '[' -z django_mailman3==1.3.11 ']' + TMPDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir + /usr/bin/python3 -m pip install --root /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /builddir/build/BUILD/python-django-mailman3-1.3.11-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/python-django-mailman3-1.3.11-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/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/bin ']' + rm -f /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-ghost-distinfo + site_dirs=() + '[' -d /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + site_dirs+=("/usr/lib/python3.13/site-packages") + '[' /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib64/python3.13/site-packages '!=' /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + '[' -d /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib64/python3.13/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT$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/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/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/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT --record /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/RECORD --output /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-record + rm -fv /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/RECORD removed '/builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/RECORD' + rm -fv /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3-1.3.11.dist-info/REQUESTED removed '/builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/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-build/python-django-mailman3-1.3.11-1.fc41.noarch-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-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-files --output-modules /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-modules --buildroot /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT --sitelib /usr/lib/python3.13/site-packages --sitearch /usr/lib64/python3.13/site-packages --python-version 3.13 --pyproject-record /builddir/build/BUILD/python-django-mailman3-1.3.11-build/python-django-mailman3-1.3.11-1.fc41.noarch-pyproject-record --prefix /usr django_mailman3 + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j8 Bytecompiling .py files below /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13 using python3.13 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/bin/add-determinism --brp -j8 /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/auth/fedora/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/auth/fedora/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/auth/fedora/__pycache__/provider.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/auth/fedora/__pycache__/views.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/auth/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/__pycache__/paginator.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/__pycache__/scrub.cpython-313.pyc: replacing with normalized version /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/__pycache__/mailman.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/__pycache__/scrub.cpython-313.opt-1.pyc: replacing with normalized version /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/lib/__pycache__/user.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/middleware/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/migrations/__pycache__/0003_sessions.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/migrations/__pycache__/0002_maildomain.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/templatetags/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/templatetags/__pycache__/d_gravatar.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/templatetags/__pycache__/bootstrap_tags.cpython-313.pyc: replacing with normalized version /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/templatetags/__pycache__/pagination.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/templatetags/__pycache__/bootstrap_tags.cpython-313.opt-1.pyc: replacing with normalized version /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_lib_auth_fedora_provider.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_bootstrap_tags.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_lib_user.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/urls_test.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_paginator.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_context_processors.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_delete_account.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_mailman.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_scrub.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/settings_test.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_forms.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_middlewares.cpython-313.pyc: replacing with normalized version /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_middlewares.cpython-313.opt-1.pyc: replacing with normalized version /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/views/__pycache__/user_adapter.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/views/__pycache__/profile.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/views/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_view_profile.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/tests/__pycache__/test_signals.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/apps.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/context_processors.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/models.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/lib/python3.13/site-packages/django_mailman3/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents Processed 71 paths Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.MG6svj + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/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,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + 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 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + PATH=/builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin + PYTHONPATH=.: + PYTHONDONTWRITEBYTECODE=1 + PYTEST_ADDOPTS=' --ignore=/builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/.pyproject-builddir' + PYTEST_XDIST_AUTO_NUM_WORKERS=8 + HOSTNAME=rpmbuild + /usr/bin/python3 -m tox --current-env -q --recreate -e py313 ============================= test session starts ============================== platform linux -- Python 3.13.0b2, 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/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11 configfile: pytest.ini plugins: django-4.8.0 collected 83 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/python-django-mailman3-1.3.11-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 ================== 82 passed, 1 skipped, 3 warnings in 40.60s ================== py313: OK (41.58 seconds) congratulations :) (41.67 seconds) + RPM_EC=0 ++ jobs -p + exit 0 Processing files: python3-django-mailman3-1.3.11-1.fc41.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.UeXXRq + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-build + cd django-mailman3-1.3.11 + DOCDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/share/doc/python3-django-mailman3 + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/share/doc/python3-django-mailman3 + cp -pr /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/README.rst /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/share/doc/python3-django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.fJOY2V + umask 022 + cd /builddir/build/BUILD/python-django-mailman3-1.3.11-build + cd django-mailman3-1.3.11 + LICENSEDIR=/builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/share/licenses/python3-django-mailman3 + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/share/licenses/python3-django-mailman3 + cp -pr /builddir/build/BUILD/python-django-mailman3-1.3.11-build/django-mailman3-1.3.11/COPYING.txt /builddir/build/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT/usr/share/licenses/python3-django-mailman3 + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-mailman3 = 1.3.11-1.fc41 python3-django-mailman3 = 1.3.11-1.fc41 python3.13-django-mailman3 = 1.3.11-1.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/BUILD/python-django-mailman3-1.3.11-build/BUILDROOT Wrote: /builddir/build/SRPMS/python-django-mailman3-1.3.11-1.fc41.src.rpm Wrote: /builddir/build/RPMS/python3-django-mailman3-1.3.11-1.fc41.noarch.rpm Child return code was: 0